72
SAP Enhancement Package 1 for SAP SRM 7.0: SRM-MDM Catalog (Catalog Content Management) Based on SAP Solution Manager Content Target Audience n System Administrators n Consultants PUBLIC Document version: 1.0 ‒ 07/12/2010

MDM Catalog

Embed Size (px)

Citation preview

Page 1: MDM Catalog

SAP Enhancement Package 1 for SAP SRM 70 SRM-MDMCatalog (Catalog Content Management)Based on SAP Solution Manager Content

Target Audience

n System Administratorsn Consultants

PUBLICDocument version 10 ‒ 07122010

Document History

Caution

Before you start the implementation make sure you have the latest version of SAP SolutionManagerContent 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

10 7122010 Initial Version

272 PUBLIC 07122010

Table of Contents

Chapter 1 Important Information About This Document 5

Chapter 2 Basic Settings for SRM-MDMCatalog (Catalog Content Management) 721 System Connections 7211 Initializing the SRM-MDMCatalog Repository 72111 Initializing the SRM-MDMCatalog Repository 72112 Setting Up Master Data Management (MDM) 10212 Portal settings for MDM 102121 Making Portal Settings for SRM-MDMCatalog 102122 Making Portal User Settings 112123 MDMWorkflows and Approval of Catalog Content 412124 Making Universal Worklist Settings for the SRM-MDMCatalog 13213 SAP Exchange Infrastructure 152131 Making SAP NetWeaver Process Integration Settings 152132 Configuring the System Landscape Directory 162133 Defining Business Systems in the Integration Directory 182134 Setting Up Integration Scenarios 182135 Editing Interface Determination 202136 More Information About SAP Exchange Infrastructure 2122 Organizational Management 21221 Define External Catalogs 212211 Catalog-Specific Role Maintenance in SAP MDM 212212 Setting Up External Web Services in SAP SRM 512213 More Information About Defining External Catalogs 24222 Configuring the Search User Interface (UI) 2423 SAP Notes 25

Chapter 3 Catalog Content Management 2731 Managing Service Content in SRM-MDMCatalog 27311 Configuring the External Integration Role 38312 Transferring Service Hierarchy from SAP ERP 28313 Transferring Service Hierarchy and Non-Hierarchical Items from RFx Response

in SAP SRM 29314 Transferring Service Hierarchy and Non Hierarchical Items from Central

Contracts (SRM) 30

07122010 PUBLIC 372

315 Import and Mapping of Catalog Data 3332 Managing Product Content in SRM-MDMCatalog 32321 Enabling Web Approval Process with iViews 43322 Import and Mapping of Catalog Data 33323 Setting Up Key Mapping for Contract Item Categories 35324 Configuring the External Integration Role 38325 Import of Contracts and Purchasing Information Records from SAP ERP 36326 Enriching Contract Data 37327 Configuring the External Integration Role 38328 Import of Products Contracts and Suppliers from SAP SRM 39329 Enrichment of Catalog Data 403210 MDMWorkflows and Approval of Catalog Content 413211 Setting Up Named Searches 463212 Enabling Web Approval Process with iViews 433213 Restriction of Searchable Catalog Items 453214 Setting Up Masks for Searching Catalog Repository 453215 Setting Up Named Searches 463216 Validations 473217 Mapping Catalog Fields to OCI Fields 623218 Extending OCI Fields 643219 Setting Up External Web Services in SAP SRM 5133 Searching in Catalog Data 53331 Configuring the Web Dynpro Search User Interface General Settings 53332 Configuring the Web Dynpro Search User Interface Display 58333 Configuring the Web Dynpro Search User Interface Search 60334 Search Functions in Catalog 61335 Mapping Catalog Fields to OCI Fields 62336 Extending OCI Fields 64337 More Information About Searching in Catalog Data 65

Chapter A Reference 67

472 PUBLIC 07122010

1 Important Information About This Document

1 Important Information About ThisDocument

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) isdelivered with the SAP Solution Manager content To implement and configure SAP SRM you mustuse SAP Solution Manager which contains the complete configuration documentation includinglinks to Customizing SAP Notes and SAP ERP documentationThis guide contains only the SAP SRM configuration documentation and references to otherdocumentation It provides you with a quick overview of the required SAP SRM configurationsettings

Caution

This guide is a supplement to the SAP Solution Manager content and does not replace it Thecomplete 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 SAPSRMmaster guide at httpservicesapcominstguides under Installation amp Upgrade GuidesSAP Business Suite Applications SAP SRM SAP SRM Server 701

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 70 (SAP SRM 70) includesthe following business functions

n SRM Strategic Sourcing Innovationsn SRM Catalog Innovationsn SRM Approval Processn SRM Continuous Innovationsn SRM Implementation Simplificationn SRM Service Procurement Innovationsn SRM PI-Independent Enterprise Servicesn SRM Supplier Collaborationn SRM Self-Service Procurementn SRM Analytics

For more information about these business functions see SAP Help Portal at helpsapcom SAPSupplier Relationship Management Business Functions and Customizing Switches

07122010 PUBLIC 572

This page is left blank for documentsthat are printed on both sides

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 2: MDM Catalog

Document History

Caution

Before you start the implementation make sure you have the latest version of SAP SolutionManagerContent 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

10 7122010 Initial Version

272 PUBLIC 07122010

Table of Contents

Chapter 1 Important Information About This Document 5

Chapter 2 Basic Settings for SRM-MDMCatalog (Catalog Content Management) 721 System Connections 7211 Initializing the SRM-MDMCatalog Repository 72111 Initializing the SRM-MDMCatalog Repository 72112 Setting Up Master Data Management (MDM) 10212 Portal settings for MDM 102121 Making Portal Settings for SRM-MDMCatalog 102122 Making Portal User Settings 112123 MDMWorkflows and Approval of Catalog Content 412124 Making Universal Worklist Settings for the SRM-MDMCatalog 13213 SAP Exchange Infrastructure 152131 Making SAP NetWeaver Process Integration Settings 152132 Configuring the System Landscape Directory 162133 Defining Business Systems in the Integration Directory 182134 Setting Up Integration Scenarios 182135 Editing Interface Determination 202136 More Information About SAP Exchange Infrastructure 2122 Organizational Management 21221 Define External Catalogs 212211 Catalog-Specific Role Maintenance in SAP MDM 212212 Setting Up External Web Services in SAP SRM 512213 More Information About Defining External Catalogs 24222 Configuring the Search User Interface (UI) 2423 SAP Notes 25

Chapter 3 Catalog Content Management 2731 Managing Service Content in SRM-MDMCatalog 27311 Configuring the External Integration Role 38312 Transferring Service Hierarchy from SAP ERP 28313 Transferring Service Hierarchy and Non-Hierarchical Items from RFx Response

in SAP SRM 29314 Transferring Service Hierarchy and Non Hierarchical Items from Central

Contracts (SRM) 30

07122010 PUBLIC 372

315 Import and Mapping of Catalog Data 3332 Managing Product Content in SRM-MDMCatalog 32321 Enabling Web Approval Process with iViews 43322 Import and Mapping of Catalog Data 33323 Setting Up Key Mapping for Contract Item Categories 35324 Configuring the External Integration Role 38325 Import of Contracts and Purchasing Information Records from SAP ERP 36326 Enriching Contract Data 37327 Configuring the External Integration Role 38328 Import of Products Contracts and Suppliers from SAP SRM 39329 Enrichment of Catalog Data 403210 MDMWorkflows and Approval of Catalog Content 413211 Setting Up Named Searches 463212 Enabling Web Approval Process with iViews 433213 Restriction of Searchable Catalog Items 453214 Setting Up Masks for Searching Catalog Repository 453215 Setting Up Named Searches 463216 Validations 473217 Mapping Catalog Fields to OCI Fields 623218 Extending OCI Fields 643219 Setting Up External Web Services in SAP SRM 5133 Searching in Catalog Data 53331 Configuring the Web Dynpro Search User Interface General Settings 53332 Configuring the Web Dynpro Search User Interface Display 58333 Configuring the Web Dynpro Search User Interface Search 60334 Search Functions in Catalog 61335 Mapping Catalog Fields to OCI Fields 62336 Extending OCI Fields 64337 More Information About Searching in Catalog Data 65

Chapter A Reference 67

472 PUBLIC 07122010

1 Important Information About This Document

1 Important Information About ThisDocument

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) isdelivered with the SAP Solution Manager content To implement and configure SAP SRM you mustuse SAP Solution Manager which contains the complete configuration documentation includinglinks to Customizing SAP Notes and SAP ERP documentationThis guide contains only the SAP SRM configuration documentation and references to otherdocumentation It provides you with a quick overview of the required SAP SRM configurationsettings

Caution

This guide is a supplement to the SAP Solution Manager content and does not replace it Thecomplete 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 SAPSRMmaster guide at httpservicesapcominstguides under Installation amp Upgrade GuidesSAP Business Suite Applications SAP SRM SAP SRM Server 701

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 70 (SAP SRM 70) includesthe following business functions

n SRM Strategic Sourcing Innovationsn SRM Catalog Innovationsn SRM Approval Processn SRM Continuous Innovationsn SRM Implementation Simplificationn SRM Service Procurement Innovationsn SRM PI-Independent Enterprise Servicesn SRM Supplier Collaborationn SRM Self-Service Procurementn SRM Analytics

For more information about these business functions see SAP Help Portal at helpsapcom SAPSupplier Relationship Management Business Functions and Customizing Switches

07122010 PUBLIC 572

This page is left blank for documentsthat are printed on both sides

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 3: MDM Catalog

Table of Contents

Chapter 1 Important Information About This Document 5

Chapter 2 Basic Settings for SRM-MDMCatalog (Catalog Content Management) 721 System Connections 7211 Initializing the SRM-MDMCatalog Repository 72111 Initializing the SRM-MDMCatalog Repository 72112 Setting Up Master Data Management (MDM) 10212 Portal settings for MDM 102121 Making Portal Settings for SRM-MDMCatalog 102122 Making Portal User Settings 112123 MDMWorkflows and Approval of Catalog Content 412124 Making Universal Worklist Settings for the SRM-MDMCatalog 13213 SAP Exchange Infrastructure 152131 Making SAP NetWeaver Process Integration Settings 152132 Configuring the System Landscape Directory 162133 Defining Business Systems in the Integration Directory 182134 Setting Up Integration Scenarios 182135 Editing Interface Determination 202136 More Information About SAP Exchange Infrastructure 2122 Organizational Management 21221 Define External Catalogs 212211 Catalog-Specific Role Maintenance in SAP MDM 212212 Setting Up External Web Services in SAP SRM 512213 More Information About Defining External Catalogs 24222 Configuring the Search User Interface (UI) 2423 SAP Notes 25

Chapter 3 Catalog Content Management 2731 Managing Service Content in SRM-MDMCatalog 27311 Configuring the External Integration Role 38312 Transferring Service Hierarchy from SAP ERP 28313 Transferring Service Hierarchy and Non-Hierarchical Items from RFx Response

in SAP SRM 29314 Transferring Service Hierarchy and Non Hierarchical Items from Central

Contracts (SRM) 30

07122010 PUBLIC 372

315 Import and Mapping of Catalog Data 3332 Managing Product Content in SRM-MDMCatalog 32321 Enabling Web Approval Process with iViews 43322 Import and Mapping of Catalog Data 33323 Setting Up Key Mapping for Contract Item Categories 35324 Configuring the External Integration Role 38325 Import of Contracts and Purchasing Information Records from SAP ERP 36326 Enriching Contract Data 37327 Configuring the External Integration Role 38328 Import of Products Contracts and Suppliers from SAP SRM 39329 Enrichment of Catalog Data 403210 MDMWorkflows and Approval of Catalog Content 413211 Setting Up Named Searches 463212 Enabling Web Approval Process with iViews 433213 Restriction of Searchable Catalog Items 453214 Setting Up Masks for Searching Catalog Repository 453215 Setting Up Named Searches 463216 Validations 473217 Mapping Catalog Fields to OCI Fields 623218 Extending OCI Fields 643219 Setting Up External Web Services in SAP SRM 5133 Searching in Catalog Data 53331 Configuring the Web Dynpro Search User Interface General Settings 53332 Configuring the Web Dynpro Search User Interface Display 58333 Configuring the Web Dynpro Search User Interface Search 60334 Search Functions in Catalog 61335 Mapping Catalog Fields to OCI Fields 62336 Extending OCI Fields 64337 More Information About Searching in Catalog Data 65

Chapter A Reference 67

472 PUBLIC 07122010

1 Important Information About This Document

1 Important Information About ThisDocument

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) isdelivered with the SAP Solution Manager content To implement and configure SAP SRM you mustuse SAP Solution Manager which contains the complete configuration documentation includinglinks to Customizing SAP Notes and SAP ERP documentationThis guide contains only the SAP SRM configuration documentation and references to otherdocumentation It provides you with a quick overview of the required SAP SRM configurationsettings

Caution

This guide is a supplement to the SAP Solution Manager content and does not replace it Thecomplete 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 SAPSRMmaster guide at httpservicesapcominstguides under Installation amp Upgrade GuidesSAP Business Suite Applications SAP SRM SAP SRM Server 701

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 70 (SAP SRM 70) includesthe following business functions

n SRM Strategic Sourcing Innovationsn SRM Catalog Innovationsn SRM Approval Processn SRM Continuous Innovationsn SRM Implementation Simplificationn SRM Service Procurement Innovationsn SRM PI-Independent Enterprise Servicesn SRM Supplier Collaborationn SRM Self-Service Procurementn SRM Analytics

For more information about these business functions see SAP Help Portal at helpsapcom SAPSupplier Relationship Management Business Functions and Customizing Switches

07122010 PUBLIC 572

This page is left blank for documentsthat are printed on both sides

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 4: MDM Catalog

315 Import and Mapping of Catalog Data 3332 Managing Product Content in SRM-MDMCatalog 32321 Enabling Web Approval Process with iViews 43322 Import and Mapping of Catalog Data 33323 Setting Up Key Mapping for Contract Item Categories 35324 Configuring the External Integration Role 38325 Import of Contracts and Purchasing Information Records from SAP ERP 36326 Enriching Contract Data 37327 Configuring the External Integration Role 38328 Import of Products Contracts and Suppliers from SAP SRM 39329 Enrichment of Catalog Data 403210 MDMWorkflows and Approval of Catalog Content 413211 Setting Up Named Searches 463212 Enabling Web Approval Process with iViews 433213 Restriction of Searchable Catalog Items 453214 Setting Up Masks for Searching Catalog Repository 453215 Setting Up Named Searches 463216 Validations 473217 Mapping Catalog Fields to OCI Fields 623218 Extending OCI Fields 643219 Setting Up External Web Services in SAP SRM 5133 Searching in Catalog Data 53331 Configuring the Web Dynpro Search User Interface General Settings 53332 Configuring the Web Dynpro Search User Interface Display 58333 Configuring the Web Dynpro Search User Interface Search 60334 Search Functions in Catalog 61335 Mapping Catalog Fields to OCI Fields 62336 Extending OCI Fields 64337 More Information About Searching in Catalog Data 65

Chapter A Reference 67

472 PUBLIC 07122010

1 Important Information About This Document

1 Important Information About ThisDocument

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) isdelivered with the SAP Solution Manager content To implement and configure SAP SRM you mustuse SAP Solution Manager which contains the complete configuration documentation includinglinks to Customizing SAP Notes and SAP ERP documentationThis guide contains only the SAP SRM configuration documentation and references to otherdocumentation It provides you with a quick overview of the required SAP SRM configurationsettings

Caution

This guide is a supplement to the SAP Solution Manager content and does not replace it Thecomplete 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 SAPSRMmaster guide at httpservicesapcominstguides under Installation amp Upgrade GuidesSAP Business Suite Applications SAP SRM SAP SRM Server 701

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 70 (SAP SRM 70) includesthe following business functions

n SRM Strategic Sourcing Innovationsn SRM Catalog Innovationsn SRM Approval Processn SRM Continuous Innovationsn SRM Implementation Simplificationn SRM Service Procurement Innovationsn SRM PI-Independent Enterprise Servicesn SRM Supplier Collaborationn SRM Self-Service Procurementn SRM Analytics

For more information about these business functions see SAP Help Portal at helpsapcom SAPSupplier Relationship Management Business Functions and Customizing Switches

07122010 PUBLIC 572

This page is left blank for documentsthat are printed on both sides

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 5: MDM Catalog

1 Important Information About This Document

1 Important Information About ThisDocument

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) isdelivered with the SAP Solution Manager content To implement and configure SAP SRM you mustuse SAP Solution Manager which contains the complete configuration documentation includinglinks to Customizing SAP Notes and SAP ERP documentationThis guide contains only the SAP SRM configuration documentation and references to otherdocumentation It provides you with a quick overview of the required SAP SRM configurationsettings

Caution

This guide is a supplement to the SAP Solution Manager content and does not replace it Thecomplete 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 SAPSRMmaster guide at httpservicesapcominstguides under Installation amp Upgrade GuidesSAP Business Suite Applications SAP SRM SAP SRM Server 701

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 70 (SAP SRM 70) includesthe following business functions

n SRM Strategic Sourcing Innovationsn SRM Catalog Innovationsn SRM Approval Processn SRM Continuous Innovationsn SRM Implementation Simplificationn SRM Service Procurement Innovationsn SRM PI-Independent Enterprise Servicesn SRM Supplier Collaborationn SRM Self-Service Procurementn SRM Analytics

For more information about these business functions see SAP Help Portal at helpsapcom SAPSupplier Relationship Management Business Functions and Customizing Switches

07122010 PUBLIC 572

This page is left blank for documentsthat are printed on both sides

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 6: MDM Catalog

This page is left blank for documentsthat are printed on both sides

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 7: MDM Catalog

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

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

21 System Connections

211 Initializing the SRM-MDM Catalog Repository

2111 Initializing the SRM-MDM Catalog Repository

Prerequisites

n The SAP Note 964991 has been applied in your SAP Supplier Relationship Management (SAPSRM) or SAP ERP system

n The SAP Note 1177780 has been appliedn The MDM Server and Import Server have been started and the SRM-MDMCatalog repository has

been loaded before the replication or checking of Customizing datan The configuration file MDMGX_Catalogtxt is downloaded to your local drive

Note

The file MDMGX_Catalogtxt is contained in SAP Note 1177780

Initializing the SRM-MDM Catalog repository comprises

1 Configuring the Extraction Framework2 Uploading the configuration file and a report3 Setting the home directory for the FTP server4 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 purchasingorganizations 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 applicationsn MDM Import Manager

07122010 PUBLIC 772

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 8: MDM Catalog

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

n MDM Data Manager

Configuring the Extraction Framework

1 Start transaction se38 in the SAP SRM or SAP ERP client system2 Enter report name MDM_GX_UPLOAD_MDMGXC1 and choose Execute

The initial screen appears3 Select Catalog as Object Type4 Select the downloaded file MDMGX_catalogtxt from your local drive5 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 system2 Select theMaintain Ports and Check-Tablesmenu item

The system opens a selection screen3 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 codes4 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 pathltSAP NetWeaver MDM 71 installation directorygtServerDistributionsgt

Note

Replace ltSAP NetWeaver MDM 71 installation directorygt with the directory name of yourMDM Server installationIf you have changed the Distribution Root Dir setting in the mdsini file (configuration file) of the MDMServer 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 system2 Choose Define Repositories and FTP Servers3 Change to Editmode4 Select the SAP_SP4_PRODUCT repository template and choose Copy As

The system opens a screen for entering the repository and FTP details5 Enter a name for the Logical Repository and change the following settings as requiredn Object Type

Using the input help select Catalogn Repository Name (Code)

872 PUBLIC 07122010

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 9: MDM Catalog

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

This must be identical to the SRM-MDM Catalog repository name in SAP MDMn FTP Server

URL to your FTP server that contains the port folder structuren MDM Root

Root folder of your local port folder structuren Client Code

Refers to the system clientn Client System Type

The entries R3 and SRM represent the SAP SRM and SAP ERP client systemsn Languages

The SRM-MDM Catalog repository supports the languagesChinese (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)

n Timeout (Minutes)6 Save your changes and return to theMDM 55 Generic Extractormain screen7 Choose Start Extraction

The system opens a screen for entering extraction parameters8 Select the ltSRM-MDM Cataloggt repository

You use the repository name you have entered in step 3 The system automatically adds the datasuch as Address of FTP Server

9 Set the FTP_DWNL indicator to activate the FTP download and choose ExecutePrior to Execute you can set the FTP_DWNL indicator to activate the FTP download and specify alocal 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 sourceSelect the relevant client system(SAP SRM or SAP ERP)

Open the Ports dropdown listand check that the followingports are available (have beenprocessed successfully) and that noexceptions have occurredn LT_Currenciesn LT_ProductGroupsn LT_UOM_ISO_Coden LT_PurchasingOrganization

Open the following lookup tablesand check their entriesn Product Groupsn Currenciesn UoM ISO Coden Purchasing Organizations (only SAP

ERP)

NoteYou can select a lookup tablevia the dropdown box in theupper left pane of the MDMData Manager Select the

07122010 PUBLIC 972

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 10: MDM Catalog

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

MDM Import Manager MDM Data Manager

(only SAP ERP) relevant client system (SAPSRM or SAP ERP)

2112 Setting Up Master Data Management (MDM)

PrerequisitesSRM-MDM Catalog 701 runs on top of SAP NetWeaver MDM 71 Refer to thecorresponding IT Scenario Configuration guide for MDM on SAP Service Marketplace athttpservicesapcominstallMDM for information on the topics listed below

ProcedureReferring to the corresponding IT Scenario Configuration guide for MDM for information youneed to

n Adjust the shipped repository structuren Make your client systems known to MDMn Provide the check tables in MDM as reference data

n Set up SAP NetWeaver Process Integration (SAP PI) if you are using SAP PI

More InformationIf you are using SAP NetWeaver Process Integration (SAP PI) seeMaking SAP NetWeaver Process IntegrationSettings [external document]

212 Portal settings for MDM

2121 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]

1072 PUBLIC 07122010

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 11: MDM Catalog

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

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The MDM business packages have been deployedFor more information see SAP Service Marketplace at httpservicesapcominstallMDM

n The SRM-MDM Catalog business packages have been deployed using SDM to deployBP_SRM_MDMsca

n You have System Administrator authorization

Procedure

1 Log on to the Portal Content Browser as a SystemAdministrator and choose System AdministrationSystem 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 forMDM Host Server Repository Name and ifrequired 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_MDMCATand SAP_SRM_MDMCAT_WFORIG

ResultYou have defined the connection properties and the system aliases

2122 Making Portal User Settings

To implement the optional process step of Enabling Web Approval Process with iViews you have toensure that the MDMworkflow tasks are assigned to a specific portal user To ensure that the portaluser gets the task in a UWL (Universal Worklist) you have to map the portal user to an MDM user

Prerequisites

n The MDM user to which the portal user is mapped is assigned the MDM roles Catalog Managerand Catalog Content ApproverFor more information see Enabling Web Approval Process with iViews (Optional) [external document]

n You have System Administrator authorizationn The target MDM repository is loaded

07122010 PUBLIC 1172

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 12: MDM Catalog

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

Procedure

1 Log on to the Portal Content Browser as a System Administrator and choose User Administrator tolocate the portal user that you want to map to an MDM user

2 Choose Modify User Mapping for System Access3 Select SAP_SRM_MDMCAT and enter the MDM user and password Save your entries4 Repeat the above process for your Administrator user5 Assign the role SRM Catalog Content Manager (comsappctsrmmdmcatrolecat_cont_mgr)

to the portal user by choosing Modify Available Roles Add the rolecomsappctsrmmdmcatrolecat_cont_mgr to the portal user

6 In the System Administrator tab choose System Configuration Portal Content Content Provided by SAPSpecialist 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 tabWorkflow appears at the top level This new tabdisplays all workflow tasks assigned to the mapped MDM user assuming that you have carried out thebusiness process stepMaking Universal Settings for the SRM-MDM Catalog [external document]

2123 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdmBased on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after import

1272 PUBLIC 07122010

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 13: MDM Catalog

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

After the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

2124 Making Universal Worklist Settings for the SRM-MDMCatalog

To use web-based approval workflows in the Portal you need to create a connection between the UWL(Universal Worklist) and the MDMWorkflow engine

07122010 PUBLIC 1372

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 14: MDM Catalog

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

Procedure

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

2 Create a new connection with the system alias SAP_SRM_MDMCAT and connector typeMdmUwlConnector Save your entriesA new connection appears in the table

3 Choose Universal Worklist Content Configuration Click to Administrate Item Types and View DefinitionsDownload the configurationMDM to your local file system

4 Open the XML file with a text editor and delete all the content in the tag ltItem Typesgt andadd the followingltItemType name=uwltaskmdmtasksSAP_SRM_MDMCATMDMSRM_CATALOG_ITEMSconnector=MdmUwlConnector defaultView=MdmViewTasks defaultAction=showMdmDe-tails executionMode=defaultgtltActionsgtltAction name=showMdmDetails groupAction=no handler=IViewLauncherreturnToDetailViewAllowed=yes launchInNewWindow=yesgtltPropertiesgtltProperty name=taskId value=$itemjobIdgtltProperty name=externalRequestEvent value=comsappctmdmapplmasteriviewseventsex-ternalsViewTaskRecordsHandlergtlt Property name=iview value=portal_contentcomsappctspecialistcomsappctsrmmdm-catrootrolecomsappctsrmmdmcatrolecat_cont_mgrcomsappctsrmmdm-catwf_itemsgtltPropertiesgtltDescriptions default=Show Record DetailsgtltActiongtltActionsgtltItem Typesgt

5 Choose Upload New Configuration and select the file you edited in the previous step Upload it withthe name MDM

6 Select OK to overwrite the old configuration7 In the section Universal Worklist Content Configuration choose Universal Worklist amp Workflow Universal

Worklist mdash Administration and select the link Cache Administration Page to clear the cache

1472 PUBLIC 07122010

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 15: MDM Catalog

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

213 SAP Exchange Infrastructure

2131 Making SAP NetWeaver Process Integration Settings

To enable communication between the SAP Supplier Relationship Management (SAP SRM) serverand the SRM-MDM catalog with the integration server you make settings in SAP NetWeaver ProcessIntegration (PI)SAP NetWeaver PI is required between SAP SRM or SAP ERP for

n Contract replication (upload from SAP SRM to the SRM-MDM repository)n Product data replication from SAP SRMn Replication of info records with material master data and contracts from SAP ERPn Transfer of supplier from SAP SRM to SRM-MDM repository

Note

SAP NetWeaver PI is not required if

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

n You do not replicate product or contract data

Prerequisites

n A system connection has been set up and configured between the SRM Server and SAP NetWeaverPI

n The Integration Server has been installedFor more information see SAP Service Marketplace at httpservicesapcominstguides

SAP NetWeaver SAP NetWeaver 70 ( 2004s) Installation

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n The SAP NetWeaver XI content for SRM Server and for SRM-MDMCatalog 30 has been imported

Note

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

Procedure

1 Enabling Use of Process Integration

07122010 PUBLIC 1572

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 16: MDM Catalog

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

For more information see SAP Solution Manager under ltproject namegt Configuration SAPSRMltreleasegt Basic Settings for SRM-MDMCatalog (Catalog Content Management) System ConnectionsSAP 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]

2132 Configuring the System Landscape Directory

To use SAP NetWeaver Process Integration (PI) as part of the Catalog Content Management businessscenario you must define the following in the System Landscape Directory (SLD)

n The systems that use SAP PI to send messages SRM Servern The systems that receive messages from SAP PI SAP MDM Server

PrerequisitesImplement SAP Note 836200

ProcedureConfigure the technical and business system landscape for

n SAP SRM Server (Role Application System)n SAP NW Integration Server (Role Integration Server)

More InformationThe figure below shows the required system connections and protocols the processes for whichthose system connections and protocols are required and a sample system landscape for the CatalogContent Management business scenario

1672 PUBLIC 07122010

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 17: MDM Catalog

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

Figure 1

The bold lines represent connections that are always required The arrows show the directionof the requestsSee the table below for more information on key topics

Topic Title Available in the SAP Help Portal(helpsapcom)

Configuring the technical systemlandscape for 3rd PartyApplications(Non-ABAPNon-Java Systems)

Technical System Landscape (SystemLandscape Directory)

SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for SAPNetWeaver Administration of SAPNetWeaver Systems Process Integration(PI)

Configuring the business systemlandscape (Registering an ExternalSystem as a Business System)

Configuring a Business System SAP NetWeaver ltreleasegt LibrarySAP Library SAP NetWeaverLibrary SAP NetWeaver by KeyCapability Process Integration by KeyCapability SAP NetWeaver ExchangeInfrastructure Design and ConfigurationTime Configuration SystemLandscape Directory in SAP ExchangeInfrastructure

Configuring Integration Scenarios Business Solution Configuration SAP NetWeaver ltreleasegtLibrary SAP Library SAPNetWeaver Library AdministratorrsquosGuide Technical Operations for

07122010 PUBLIC 1772

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 18: MDM Catalog

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

Topic Title Available in the SAP Help Portal(helpsapcom)

SAPNetWeaver Administration of SAPNetWeaver IT Scenarios EnablingApplication-to-Application ProcessesTasks

2133 Defining Business Systems in the IntegrationDirectory

To define the technical communication parameters between the Integration Server and theSRM-MDMCatalog business system configured in the System Landscape Directory (SLD) you definebusiness systems in the Integration Directory

Prerequisites

n The required business systems have been defined in the SLDn 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 empty2 In the Select Business System step choose the business system for the SRM-MDM Catalog3 Deselect the checkbox Create Communication Channels Automatically

2134 Setting Up Integration Scenarios

To automate the definition of receiver routing and interface routing you import the predefinedSRM-MDM Catalog integration scenario from the Integration Repository and generate thecorresponding Configuration Scenario

Prerequisites

n The integration scenario SRM_MDM_Catalog is used for the SRM_MDM_Catalog for productprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The integration scenario SRM_MDM_Catalog_30 is used for the SRM_MDM_Catalog in serviceprocurement It is available in the namespace httpsapcomxiSRM-MDMCatalog

n The System Landscape Directory (SLD) is preconfigured

1 Choose Integration Builder Configuration

1872 PUBLIC 07122010

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 19: MDM Catalog

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

2 Choose Tools Transfer Integration Scenario from Integration Repository3 Select the predefined integration scenario and assign the (customer-specific) name you want to

use for your scenario ltCustomer_Specific__SRM-MDM_catalog_scenariogtThe integration scenario wizard opens

4 Follow the configuration steps in the left-hand frame of the integration scenario wizard5 Select the corresponding view of the integration scenario6 Under Assign Services select the relevant business systemsn The business system for the SRM-MDM Catalogn The business system for SAP SRM or SAP ERP

7 Configure Connections

Follow On Activities

n Create a receiver channel for the adapter type XI for each connection For more information seeCreating Communication Channels with Template [external document]

n In the Create Configuration Objects dialog box set the following indicatorsl Generation

l Receiver Determination

l Interface Determination

l SenderReceiver AgreementFor more information see Editing Interface Determination [external document]

n Manually create business services for normal hierarchy upload and price uploadn Manually assign the communication channels to the above business servicesn Manually branch messages

Branching messages enables them to reach multiple destinations for example the business servicesdefined for the normal hierarchy and price uploadTo enable this add business service to the Service column of the configured receivers table in thereceiver determination The Conditions column must be blank

n Manually create communication channels for _price business scenariosn Manually create receiver agreements for _price business scenariosn Manually create the interface determinations related to _price business scenariosn Manually create the two new inbound interfaces related to hierarchies for sender service ERP

More InformationSee the SAP Help Portal at httphelpsapcom SAP NetWeaver SAP NetWeaver 70 ( 2004s)SAP NetWeaver Library SAP Netweaver by Key Capability Process Integration by Key Capability SAPNetWeaver Exchange Infrastructure Design and Configuration Time

07122010 PUBLIC 1972

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 20: MDM Catalog

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

2135 Editing Interface Determination

To ensure that the upload of contract and product data uses the correct interfaces you edit theinterface determination in the integration directory for the scenario you defined in the businessprocess 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 sublevels3 Open the node Interface Determination

The inbound interfaces are displayed Three of the interfaces handle contracts one productsand five services

Interface Used For

MDMContractDataTransmission4ProductID_In Contract items containing a product ID

MDMContractDataTransmission4ProductCate-gory_In

Contract items containing a product category

MDMContractDataTransmission4SupplierPart-Number_In

Contract items containing a Supplier Part Number

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

ERPMSSUploadStructure_In Hierarchy Structure (headers and outlines) fromERP 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 (CatalogType Code 14)

MDMHierarchyTransmissionNonHierarchy_In Items NOT associated to any Hierarchy from SRMRFx ( Catalog Type Code 08)

MDMHierarchyTransmissionStructure_In Hierarchy Structure (headers and outlines) fromSRM 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 ldquoUsed forrdquocolumn) the system routes this data to several interfaces

4 Choose Standard as the type of Interface Determination5 Deselect theMaintain Order At Runtime indicator

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

2072 PUBLIC 07122010

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 21: MDM Catalog

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

6 Navigate into the empty Condition fieldThe Condition Editor opens

7 Specify the NamespacelthttpsapcomxiEBPgt and the corresponding namespace Prefix nr1 for thefirst interface that you are setting up

8 Click a line to open the expression editor and set up the Xpath expressionEach line of the condition editor represents one operand of the condition You can combine twooperands using the following Boolean operatorsn AND

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

n NOT

Note

For more information on the Xpath expression see SAP Note 1177780

More InformationSetting Up Integration Scenarios [external document]

2136 More Information About SAP Exchange Infrastructure

Perform the following activity in Customizing for SAP SRMSAP Supplier Relationship Management SRM Server Cross Application Basic Settings Enable Use of

Exchange Infrastructure

22 Organizational Management

221 Define External Catalogs

2211 Catalog-Specific Role Maintenance in SAP MDM

To use the SRM-MDM Catalog you need to assign catalog-specific roles in SAP MDM ConsoleYou assign the corresponding roles for the following tasks

07122010 PUBLIC 2172

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 22: MDM Catalog

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

Task Role Description

Manage catalog content Catalog Manager Responsible for importingmanaging and classifying productand contract data in the MDMImport Manager and MDM DataManager

Approve catalog content Catalog Content Approver Responsible for approving orrejecting catalog items in theSRM-MDM Catalog workflow

Launch catalog search Catalog User This role refers to the search usersassigned to the catalog Web serviceYou configure this Web service inCustomizing under SAP SupplierRelationship Management SRMServer Master Data ContentManagement Define External WebServices

Configure catalog search UI UI Configuration Manager Responsible for setting upuser-specific configuration forusers who are assigned the CatalogUser roleThe owner of this role is authorizedto configure the Java-based WebDynpro search UI and the opencatalog interface (OCI) mapping

Upload content to catalog External Integration Responsible for trackingresponsibilities differentiateimports and compare updatesoriginating from humaninteraction with the updatesthat are system-driven

2212 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2272 PUBLIC 07122010

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 23: MDM Catalog

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

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate featureFor this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

07122010 PUBLIC 2372

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

32 Managing Product Content in SRM-MDM Catalog

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

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

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

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

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

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

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

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

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

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

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

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

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

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

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

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 24: MDM Catalog

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

Parameter Name Parameter Value Type Additional Information

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

2213 More Information About Defining External Catalogs

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

222 Configuring the Search User Interface (UI)

For more information see SAP Help Portal athttphelpsapcomsaphelp_srm70helpdataen2a37290780d74681b6a6ee55ec0ba752contenthtm

2472 PUBLIC 07122010

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

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

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

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

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

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

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

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 25: MDM Catalog

2 Basic Settings for SRM-MDM Catalog (Catalog Content Management)23 SAP Notes

23 SAP Notes

The following SAP Note applies 1171711

07122010 PUBLIC 2572

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

You can export the MSS and contract hierarchy data together in one message if you select bothof them in the export transaction

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 26: MDM Catalog

This page is left blank for documentsthat are printed on both sides

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

You can export the MSS and contract hierarchy data together in one message if you select bothof them in the export transaction

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 27: MDM Catalog

3 Catalog Content Management

3 Catalog Content Management

This section describes the settings that are required to run the Catalog Content Managementscenario You can find a scenario description in SAP Solution Manager under ltproject namegtScenarios Catalog Content Management Select the Documentation tab

31 Managing Service Content in SRM-MDM Catalog

The processManaging 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 ltproject namegt ScenariosCatalog Content Management Business Processes Managing Service Content in SRM-MDM Catalog

311 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting

07122010 PUBLIC 2772

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

You can export the MSS and contract hierarchy data together in one message if you select bothof them in the export transaction

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 28: MDM Catalog

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

312 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 contracthierarchies from the ERP system

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-Structure_In

MDMHierarchy-Transmission

06 (MSS) and 12(contracts)

CatalogueUp-dateNotication

CatalogueUp-dateNotica-tion_Out

ERPMSSUpload-HierItem_In

MDMHierarchy-Transmission

07 (MSS) and 14(Contracts)

Note

You can export the MSS and contract hierarchy data together in one message if you select bothof them in the export transaction

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure product groups and purchasing organizations) has been initialized

2872 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 29: MDM Catalog

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

n The Model Service Specification (MSS) or contracts to be uploaded exists in the SAP ERP systemand does not have the status Blocked or Configurable MSS

n The transactionMECCM is available in the SAP ERP system for uploading the MSS into theSRM-MDM Catalog

Procedure

1 RunMECCM in the SAP ERP system you are using for testing2 Enter the catalog name in the Catalog Designation sub-screen This is a mandatory field3 Enter the date on which the price of the service master items is to be calculated4 Deselect the Test Run checkbox and choose Execute5 Check the Log for any errors

ResultThe service hierarchy has been transferred from SAP ERP to SAP SRMUse transaction sxmb_moni to check that the XML containing the hierarchical structure and the XMLcontaining the service items have been passedTo check that the service hierarchy has been transferred to the catalog you can check the catalogUI to see if Categories displays the header that was imported into the repository When you select theheader the entire hierarchy (outlines and services) is displayed in the services table Check if theoutlines service items and their prices correspond to the ones uploaded from SAP ERP

313 Transferring Service Hierarchy and Non-HierarchicalItems from RFx Response in SAP SRM

1 Log on as Purchaser2 Create a new RFx with hierarchical and non hierarchical items3 Publish the RFx4 Log on as Bidder5 Create an RFx Response6 Log on as Purchaser7 Accept the RFx Response8 Choose Responses and Awards and choose the RFx response from the Bidder9 Choose Items tab10 Choose Publish to Catalog in the item table to transfer the items to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

07122010 PUBLIC 2972

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 30: MDM Catalog

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

314 Transferring Service Hierarchy and Non HierarchicalItems from Central Contracts (SRM)

You use this function to transfer service hierarchies and non hierarchical items with contract datafrom the SAP Supplier Relationship Management (SRM) to the SRM-MDM Catalog repositoryusing the MDM Import Server

Integration

The following table contains the message interface that the system uses to transfer contracthierarchies from the SRM system to the MDM Catalog repository

PI Message Type PI OutboundInterface

MDM InboundInterface

MDM MessageType

Catalog Type Code

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionStruc-ture_In

MDMHierarchy-Transmission

12

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMHierarchy-TransmissionFunc-tional_In

MDMHierarchy-Transmission

14

CatalogTransmis-sion

CatalogUpdateNoti-cation_Out

MDMContract-DataTransmis-sion4ProductID_In

MDMContract-DataTransmission

03

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure and product groups) has been initialized

Procedure

1 Log on as Purchaser2 Create a new Contract of type Central Contract (CCTR) with hierarchical and non hierarchical items3 In Header set the value for Distribute Contract to Catalog to Yes4 Release the contract to transfer it to the catalog

ResultItems 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 SRMto SAP Process Integration (SAP PI)

2 Check that the transferred hierarchy has been passed to the catalog and is visible in the catalog UI

3072 PUBLIC 07122010

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 31: MDM Catalog

3 Catalog Content Management31 Managing Service Content in SRM-MDM Catalog

315 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been createdn 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

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import Server

07122010 PUBLIC 3172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 32: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

You use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

32 Managing Product Content in SRM-MDM Catalog

The processManaging Product Content in SRM-MDM Catalog consists of the following process steps

1 Import product hierarchy2 Upload supplier product data3 Map imported hierarchy and products to repository4 Transfer info records and contracts from ERP5 Transfer product data from SRM6 Transfer contract data from SRM7 Enrich product data8 Approve product data9 Define masks and named searches10 Define validations11 Enable web content

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog

321 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product recordsn Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

3272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 33: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

322 Import and Mapping of Catalog Data

You use this function to import and map service hierarchy data to the SRM-MDM Catalog

PrerequisitesTo use the MDM Server for an automatic upload of data

n The import maps have been set up with the MDM Import Managern References fromMDM inbound ports to the import maps have been created

07122010 PUBLIC 3372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 34: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The automatic import has started and is dependent on your operating system For example inMicrosoft Windows the automatic import is started as a service

FeaturesIn the MDM Import Manager you can

n 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 thevalue in all records

n Save your mappings and conversions in an import map in the SRM-MDM Catalog repository forreuse during future imports

Example

You can create import maps for importing service structures

In the MDM Import Server the following activities take place

n Automatic upload of datan Record Filtering for Catalog Import

For more information see the Data Management Reference Guide on SAP Service Marketplace athttpservicesapcominstallMDM

IntegrationTo use this function you need the following SAP NetWeaver Master Data Management (SAPNetWeaver MDM) components

n MDM Import ManagerProvides data transformation capabilities to preprocess the source data one field at a time priorto the importFor more information about using the MDM Import Manager see the Import Manager ReferenceGuide on SAP Service Marketplace at httpservicesapcominstallMDM

n MDM Import ServerYou use this module for an automatic upload of data

More Information

n Import of Products Contracts and Suppliers from SAP Supplier Relationship Management (SAP SRM) [externaldocument]

n Import of Contracts and Purchase Information Records from SAP ERP [external document]

3472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 35: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

323 Setting Up Key Mapping for Contract Item Categories

To set up the key mapping for

n Pre-delivered content of the contract item categories tablesBy default this table contains the following entriesl Normal

l Product Categoryn Your own client systems that you have created (if applicable)

SAP delivers editable key mappings for the SAP Supplier Relationship Management (SAP SRM)and SAP ERP client systems for example

Default Item Category Name Client System Key

[x] Normal SAP ERP ltNULLgt

[x] Normal SAP SRM Normal

Prerequisites

n You have logged on to the SAP MDM Data Managern The SRM-MDM Catalog repository is loadedn The SRM-MDM Catalog repository is switched to Recordmoden The SRM-MDM Catalog repository is setup for Product informationn

Procedure

1 Select the table Contract Item Categories in the upper left pane2 Open the context menu of a record with the right mouse button and select Edit Key Mapping The

system opens a dialog window for maintaining key mappings3 Choose Add to enter an additional key mapping4 Adjust the new entry5 Select your client system6 Using the existing entries as a template set the key

Repeat Steps 2 ‒ 4 for each contract item category

324 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updates

07122010 PUBLIC 3572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 36: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

In the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut downn The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

325 Import of Contracts and Purchasing InformationRecords from SAP ERP

You use this function to import contracts and purchasing information records (PIR) from SAP ERP tothe SRM-MDM Catalog repository using the MDM Import Manager

PrerequisitesSAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction of currenciesunits of measure product groups and purchasing organizations) has been initialized

3672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 37: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Features

n The SAP ERP system transfers the values of the following fieldsl Material number

l Materialservice group

l Price

l Order unit

l Planned delivery time

l Vendor number

l Contract number and contract item number

l Number of purchasing info record

l Purchasing organization

n The SRM-MDMCatalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)

Using the transaction MECCM in the SAP ERP system you replicate the supplier and materialinformation from contract items or PIRs to the SRM-MDM Catalog repository

IntegrationThe following table shows the message interface that is used by the system to transfer contract itemsand PIRs from SAP ERP

Message Interface for transfer of contract items and PIRs

XI Message Type XI Outbound Interface MDM Inbound Interface MDMMessage Type

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMContractData-Transmission

CatalogueUpdateNoti-cation

CatalogueUpdateNoti-cation_Out

MDMContractData-Transmission4Produc-tID_In

MDMInfoRecordData-Transmission

Note

You can export the PIR and contract item data together in one message if you select them togetherin the export transaction

326 Enriching Contract Data

To enrich contract data you use the Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI to

n Enrich contract data of uploaded productsn Transfer contracts when you require the discounts and price scales

07122010 PUBLIC 3772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 38: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

The BAdI implementation supports the following category-specific conditions

n Item Category Normall Price (ContractQuotation)

l Price (ContractQuotation) with scales

l Discount (Percent)

l Discount (Percent) with scalesItem Category Product Categoryl Discount (Percent)

Note

Scales that have an interval starting with a lower bound value of 0 are changed to 1

PrerequisitesThe SRM-MDM Catalog repository is setup for Product information

Procedure

1 In Customizing for SAP Supplier Relationship Management (SAP SRM) choose SAP SupplierRelationship Management SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces Change SAPXML Outbound Mapping (BBP_SAPXML1_OUT_BADI)

2 Copy the delivered default implementation of the above BAdI to the customer namespace3 Set up the interface method Catalog and set the filter to Catalog4 Save and activate your custom implementation

327 Configuring the External Integration Role

You use this technical role to track responsibilities differentiate imports and compare updatesoriginating from human interaction with those originating from system-driven updatesIn the standard system this role is assigned to the System that is the human user However bydefault the MDM Import Server uses the Administrator user that is assigned the Administrator roleto upload external data through the XML bound interface and the file systemIn this procedure you change the default user for uploading external data in the MDM ImportServer from Administrator to System

Prerequisites

n The user System is assigned the role External Integrationn The basic configuration of the MDM Import Server is completen The MDM Import Server is shut down

3872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 39: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n The SRM-MDM Catalog repository is setup for Product information

Procedure

1 In the installation directory open the mdisini file2 Enter the appropriate name for the Server setting3 Start the MDM Server and then the Import Server4 In the MDM Console load the catalog repository

This initiates system creation of a database-specific entry for your catalog repository in themdisini file You change this entry as described below

5 Shut down the Import Server and modify the repository section of the mdisini and change thefollowing data

Old New

login = Admin login = System

password = password = ltyour_passwordgt

Note

By default the user System has the password system In the interests of security change this passwordduring configuration

328 Import of Products Contracts and Suppliers from SAPSRM

You use this function to transfer product contract and supplier data from SAP Supplier RelationshipManagement (SRM) to the SRM-MDM Catalog repository using the MDM Import Manager

Prerequisites

n SAP Note 1177780 has been applied and the SRM-MDM Catalog repository (extraction ofcurrencies units of measure and product groups) has been initialized

n To ensure that changes to a product such as price availability and so on are updated when a newSAP SRM document is being created the field NEW_ITEM-EXT_PRODUCT_IDmust be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SAP SRM server system The flag Validate Product Data from SAP Enterprise Buyermust be set for the relevant catalog

n To include price scales discounts and discount scales in your catalog data contract data must beenriched For more information see SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Managing Product Content in SRM-MDM Catalog EnrichProduct Data Select the Configuration tab

07122010 PUBLIC 3972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 40: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n To transfer additional data together with a contract such as price scales discounts and discountscales the standard implementation of Business Add-In (BAdI) BBP_SAPXML1_OUT_BADI mustbe modified The BAdI is available in the Customizing for SAP Supplier Relationship ManagementSupplier Relationship Management reg SRM Server Business Add-Ins (BAdIs) SAP XML Interfaces

Change SAP XML Outbound Mapping (BBP_SAPXML1_OUT_BADI)Each time a user selects items from the catalog adds them to the shopping cart and posts thepurchase order this BAdI updates contract data in the SAP SRM systemFor more information see SAP Solution Manager ltproject namegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing Product Content in SRM-MDMCatalog Transfer Product Data from SRM and Transfer Contract Data from SRM

FeaturesThe SRM-MDM Catalog stores contract prices per catalog item together with the contract ID theamount and the contract item category (normal or product category)The table below contains the reports and transactions used in these activities

Activities for Import of Products Contracts and Suppliers from SAP SRM

Report Transaction Description

BBP_CCM_TRANSFER_CATA-LOG

BBP_CCM_TRANSFER Product data is sent from the SAPSRM system to the SRM-MDMCatalog repository

SRMMDM_CTR_TRANSFER SRMMDM_CTR_TRANSFER Contracts are sent from the SAPSRM system to the SRM-MDMCatalog repository

ROS_SUPPLIER_SEND_TO_CATALOG

Not Available Suppliers are uploaded from theSAP SRM system to the SRM-MDMCatalog repository

329 Enrichment of Catalog Data

You use this function to enrich product data in the MDM Data ManagerExamples of enriching data include

n Editing the product classification structure (the taxonomy) for example adding a new nodeto the category table

n Adding new images to the repositoryn Adding validations or assignments and running them against records For more information

see Validations [external document]

4072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 41: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

FeaturesYou can for example

n Add a new category to the taxonomy To do so open the taxonomy mode select a categoryname and add a siblingAfterwards you create new attributes for the selected category For more informationsee the Data Management Reference Guide for MDM 71 on SAP Service Marketplace athttpservicesapcominstallMDM

n Add new imagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

n Enrich the product data To do so match items sent by suppliers with existing product andmaterial IDs (imported either from SAP Supplier Relationship Management (SAP SRM) or SAPERP) and add the product IDs to the records that the supplier submitted

n Run a validation against a record (in the MDM Data Manager) and execute it either manually orautomatically

n Add back-end product IDs to catalog items

Note

You do this afterl Importing product IDs (from SAP SRM) or material IDs (from SAP ERP)

l Matching them against the catalog items in your repository

3210 MDM Workflows and Approval of Catalog Content

You use these functions in the MDMData Manager to create design and execute workflowsThe import change or creation of records triggers MDM workflowsYou use these MDM workflows for functions such as approving catalog content for example aworkflow Automatic Approval leads to the following result

n All supplier items containing a price change of less than 5 are automatically updated andreceive the status Approved

n Supplier items that did not successfully pass the check specified in the validation expression receivethe status To Be Approved

FeaturesYou can define MDMworkflows add records or add model workflow steps that include for examplevalidations or assignmentsFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallmdm

07122010 PUBLIC 4172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 42: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Based on specific trigger actions (such as import or update) you can start workflows automaticallyFor example in the MDM Import Manager you can configure a map that launches and assignsrecords to a workflow after importAfter the workflow job has been launched a workflow job task appears for the responsible user forexample the owner of the Catalog Content Approver role On completion of the workflow step the usersends the workflow to the next step

Example

AnMDMworkflow could comprise the following workflow steps that are triggered after new catalogcontent is imported and records are assigned the status Checked-Out

1 Start2 Enrich Data

Users with the MDM role Catalog Manager can review the content of the records and if requiredmodify records in the MDM Data Manager

3 ApproveUsers with the MDM role Catalog Content Approver can approve or disapprove records or splitrecords into new workflow tasks to delegate the job to other users

4 Set StatusItems are updated with the new value that indicates the approval status such as Approved

5 StopAll records are checked in automatically

IntegrationMDM workflows are designed using Microsoft Visio 2003 Standard These workflows comprisepredefined steps for user activities and workflow elements such as validations approvals andnotifications

Caution

MDMworkflows run independently of the SAP workflow framework and are not the same as otherSAP SRM workflows

More InformationValidations [external document]Enabling Web Approval Process with iView (Optional) [external document]

3211 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM Data

4272 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 43: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Manager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3212 Enabling Web Approval Process with iViews

When new catalog content is uploaded to the SRM-MDMCatalog you have to approve it Approvingcatalog content involves tasks such as

n Approving or rejecting product records

07122010 PUBLIC 4372

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 44: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Setting approval-status checkboxes for recordsn Role-based task distribution

n Automatic check-in of approved records

You use iViews to define a web-based process so that users can carry out the tasks listed above SAPdelivers a set of predefined iViews for this purpose

Prerequisites

n The SAP components required for the SRM-MDM Catalog 30 business scenario have beeninstalledFor more information see SAP Note 1177780

n You are assigned the role Catalog Manager or Catalog Content Approver

Recommendation

We recommend assigning each workflow step to anMDM role instead of anMDMuser SAP supportsthe two MDM roles Catalog Manager and Catalog Content Approver

Procedure

1 Define an MDM workflow for your approval processFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

2 Deploy MDM business packagesFor more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

3 Deploy MDM SRM catalog business packages using SDM for deploying BP_SRM_MDMsca4 Make Portal settings for the SRM-MDM Catalog

For more information seeMaking Portal Settings for the SRM-MDM Catalog [external document]andMaking Portal User Settings [external document]

5 Make Universal Worklist (UWL) settings for the SRM-MDM CatalogFor more information seeMaking Universal Worklist Settings for the SRM-MDM Catalog [externaldocument]

More InformationFor more information about MDMWorklows seeMDMWorkflows and Approval of Catalog Content [externaldocument]

4472 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 45: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

3213 Restriction of Searchable Catalog Items

In this process you make the settings required to reduce the number of catalog items available in acatalog search by using the following alternatives for your catalog

Procedure

n Setting Up Masks for Searching the Catalog Repository [external document]n Setting Up Named Searches [external document]

3214 Setting Up Masks for Searching Catalog Repository

To restrict the number of search items that a user can retrieve when running a search in theSRM-MDM Catalog the Catalog Manager or Administrator

n Defines masks in the SAP MDM Data Managern Assigns products to the mask

ProcedureYou have two options for restricting catalog access using masks

n Option 1Specify existing masks in Customizing for SAP Supplier Relationship Management (SAP SRM) ofthe catalog Web service Per Web Service you specify one mask and one user See Setting Up ExternalWeb Services in SAP SRM [external document]Configure entries in the catalog web services as follows1 Enter the Parameter name as mask2 Enter the relevant parameter value3 Set the type to Fixed Value

n Option 2Assign the masks to roles and specify constraints forMasks table in the MDM Console as follows1 Navigate via Admin Roles 2 Select the Tables and Fields tab3 UnderMasks select one or more values in the Constraints column

Note

The settings in the MDM Console option have higher priority and overrule the masksetting in the SRM Web service In the URL that accesses the search user interface (UI) ofthe SRM-MDM catalog the mask and user parameters are independent from each otherHowever in the search UI you can also use the mask parameter to restrict the scope ofproducts available in the search result

07122010 PUBLIC 4572

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 46: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

To adjust an existing mask you can replace or remove products from the maskTo update several masks at a time in the Recordsmenu chooseModify Mask You can modify themask and add a search selection to the maskIn the SRM Customizing of the catalog Web service you specify a mask for accessing the catalogTo create and assign products to a mask proceed as follows

1 In the SAP MDM Data Manager create a mask2 Run a search to create a result set of the products you want to group in the mask3 Select the relevant products and choose Add to Mask

Note

You also have the option of passing the parameter mask dynamically with a BAdI For moreinformation see the Customizing for SAP Supplier Relationship Management Supplier RelationshipManagement SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc)Transfer Additional Parameters

ResultYou have set up a mask that you can apply to a runtime search to limit the set of catalog item recordsin the SRM-MDM Catalog Search UI

3215 Setting Up Named Searches

To reduce the number of searchable catalog items use the SAP NetWeaver Master Data Management(SAP NetWeaver MDM) Named Searches function You can create named searches in MDM DataManager and use them as an alternative to masks You can apply a named search by means of thenamedsearch parameter in the configuration of your catalog Web Services See Setting Up ExternalWeb Services in SAP SRM [external document]You also have the option of passing the parameter namedsearch dynamically with a BAdI For moreinformation see the Implementation Guide for SAP Supplier Relationship Management SRM ServerBusiness Add-Ins (BAdIs) External Web Services (Catalogs Vendor Lists etc) Transfer Additional Parameters

Prerequisites

n In SAP MDMData Manager the Named Searches have been added with relevant names and assignedto the Named Searches lookup table

4672 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 47: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

You can specify any name for example a name that refers to a user group such as Catalog forManagers You can assign authorizations for users who are allowed to create or change NamedSearches For more information see the MDM 71 Data Manager Reference Guide available at SAPService Marketplace httpservicesapcominstallMDM

Procedure

1 Open the MDM Data Manager and change to Recordmode2 Run a search to create a search result3 Open the Searchmenu4 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 the Prerequisites

Configure entries in the catalog web services as follows

1 Enter the parameter name as namedsearch2 Enter the corresponding parameter value3 Set the type as Fixed Value

ResultYou have set up a search constraint that you can apply to a runtime search to limit the set ofsearchable catalog item records in the SRM-MDM Catalog Search UI

3216 Validations

You use this SAP NetWeaver Master Data Management (SAP NetWeaver MDM) function to testwhether certain conditions are true or false

PrerequisitesYou have defined the validations For more information see SAP Solution Manager under ltprojectnamegt Scenario SAP SRMltreleasegt Catalog Content Management Business Processes Managing ProductContent in the SRM-MDM Catalog Define Validations

FeaturesYou define and execute validations in the MDM Data Manager by specifying a correspondingvalidation expression in the MDM expression editor An expression comprises field names attributenames lookup values attribute text values operators and functions that you either select or entermanuallyYou can execute validations interactively automatically (in workflows) or via APIsValidations are used to

07122010 PUBLIC 4772

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 48: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

n Approve catalog content in workflowsn Define complex tests for all types of conditions and then run those tests against one or more

records If you select all records the validation runs against the complete catalog

In Record Mode validations are used to

n Check a record for consistency or wrong field valuesn Check whether a record has the correct values so that it can be successfully transferred to a client

system (such as the Open Catalog Interface (OCI) interface)

For more information see the Data Management Reference Guide for MDM 71 on SAP ServiceMarketplace at httpservicesapcominstallMDM

IntegrationAssignmentsYou can use assignments in combination with validations or as an alternative to validations Likevalidations assignments are also Excel-like formulas However in contrast to validations assignmentsdo not simply return a TRUE or FALSE value but write the result value of the validation expressioninto an assigned field for example the value of the Item Status field of the main table

Example

You can set up an assignment that calculates the exact percentage of a price change in the catalogitems imported from a supplier

ExampleYou set up price validations to

n Compare the list price of a catalog item to the contract pricen Compare the price update of a catalog item transferred by a supplier to the existing price of this

item in the catalog

More InformationMDMWorkflows and Approval of Catalog Content [external document]

3217 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individuallyn 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

4872 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 49: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 4972

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 50: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

3218 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

5072 PUBLIC 07122010

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 51: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

Figure 2 OCI Fields

5 Save the changed XML file6 Import the changed XML file

3219 Setting Up External Web Services in SAP SRM

To use the SRM-MDM Catalog with SAP Supplier Relationship Management (SAP SRM) andto access the SRM-MDM Catalog via URLs from SAP SRM applications you must set up externalWeb Services in SAP SRM

Procedure

1 To create a Web Service with an ID such as SRM-MDM Catalog see Customizing for SAP SupplierRelationship Management under SRM Server Master Data Content Management Define ExternalWeb Services (Catalogs Supplier Lists etc)

2 To assign the catalog to a particular purchasing organization enter the organization in the PurchOrganization field

3 Under Additional Functions in the Product Catalog set the following indicatorsn Display Product Data Again in Catalog

Enables using the detail feature for the Open Catalog Interface (OCI) so that when the Detailsoption is selected in the overview list of catalog items product details are displayed

n Validate Product Data From SAP SRMEnables the use of the OCI validate feature

07122010 PUBLIC 5172

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 52: MDM Catalog

3 Catalog Content Management32 Managing Product Content in SRM-MDM Catalog

For this feature to work the field NEW_ITEM-EXT_PRODUCT_ID must be filled with thecatalog database key of the product when the product is transferred for the first time from theproduct catalog to the SRM Server System The system checks if products are still availablein the catalog and if the price is still up to date If the product data has changed the currentdata is transferred to SAP Enterprise Buyer

n Cross-Catalog SearchEnables the selected catalog to be searched by a keyword search that expands over all catalogWeb Services having this indicatorIn 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 displayedas integrated catalogs

4 Maintain the parameters listed below taking into account the additional information

Parameter Name Parameter Value Type Additional Information

na httpltJ2EEserver

J2EEportgtSRM-MDMSRM_MDM

URL RequiredltJ2EEservergt is thehost onwhich theJ2EE server is installed ltJ2EEportgtisthe http port of the J2EE server

username ltyour_user_namegtRefers to the user in SAPMDM(not the end user startingthe catalog search in SRM)

Fixed Value RequiredThe value can be that of any usermaintained for the catalog repositoryin SAP MDM Console AdminUsers

password ltyour_passwordgt Fixed Value Required

server ltyour_MDM_servergt[ltMDMServer Host ngt]

Fixed Value RequiredSee SAP Note 1170807

repositoryType ltRepositoryTypegt[ltRepository Typengt]

Fixed Value OptionalSee SAP Note 1170807

catalog ltSRM_MDM_CATALOGgt Fixed Value RequiredThe name of your catalog repositoryin SAP MDM

unilanguage SY-LANGU SAP-Field RequiredThe system uses the logon languageof SRM

datalanguage For exampleltENgtorSY-LANGU

Fixed ValueOrSAP-Field

RequiredThis setting controls the languagedependent fields of your catalogrepository

5272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 53: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

Parameter Name Parameter Value Type Additional Information

mask ltyour_mask_namegt Fixed Value Optional

NoteIf you do not specify a mask all usershave the same unrestricted access tothe catalog

namedsearch ltyour_named_search_namegt Fixed Value Optional

NoteIf you do not specify a named searchall users have the same unrestrictedaccess to the catalog

HOOK_URL Return URL Required

returntarget _parent Fixed Value Required This parameter determinesand informs the catalog to whichtarget OCI data has to be returned

1hwc_search False if you do not want to useleft-hand wildcards

Fixed Value Optional For more information seeSAP Note 1147662

33 Searching in Catalog Data

The process Searching in Catalog Data consists of the following process steps

1 Search for items2 Transfer data to procurement system

You can find a process description in SAP Solution Manager under ltproject namegt ScenariosCatalog Content Management Business Processes Searching in Catalog Data

331 Configuring the Web Dynpro Search User InterfaceGeneral Settings

To configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for

n General behavior for example the availability of the shopping cart preview

n Open Catalog Inteface (OCI) mappingThe OCI Mapping can be configured to be search user dependent

n User ConfigurationIndividual Settings

07122010 PUBLIC 5372

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 54: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

Assign the role Catalog User for users in MDM console requiring access to the Search User InterfaceFor more information see Catalog-Specific Role Maintenance in SAP MDM [page 21]You can configure the settings for individual catalog users to customize the way in which theycan view and use the Catalog User Interface

Note

In the standard a configuration is assigned to the Default User The Default User is used for all searchusers who are not assigned individual settings

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL to access the configuration UIhttpltJ2EEserverJ2EEportgtSRM-MDMSRM_MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under RolesFormore information see Catalog-Specific Role Maintenance in SAP MDM [page 21]

5472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 55: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

3 Select the configuration options as listed below for the Default User or for each search user thatrequires a user-specific configuration You can select the user from the list in User-SpecificConfiguration

General Tab Shopping Option

Configuration Option Possible Settings Additional Information

Cart Radio Button This setting disables the CartPreview and transfers the itemsdirectly to the external shoppingcart

Cart Preview Radio Button This setting enables the CartPreview which enables you to viewand modify the selected itemsbefore transferring them to theshopping cart application

Catalog Exploring (Display Only) Radio Button This setting is for display onlyPurchasing items is not possible

Product Radio Button This setting must be set to Yesif the user wants to view theproduct catalog

Service (MSS) Radio Button This setting must be set to Yes ifthe user wants to view the servicecatalog

Note

For a specific SRM-MDM Catalog repository you can configure the SRM-MDM Catalog SearchUI for product or for service information If you setn Service (MSS) to yes you only need to perform further configuration for OCI mapping and for

the settings in the tab Customize SearchIf the Search UI is configured as Service Catalog you can make the configuration settings onlyin the Customize Search and the other options cannot be changed

n Product to yes you need to perform further configuration for all settings

General Tab Item Display Criteria

Configuration Option Possible Settings Additional Information

List View Available YesNo Enables the display of List View in atabular format in which you cansort the items Images are alsoavailable

07122010 PUBLIC 5572

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 56: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Context View Available YesNo Enables or disables the display ofitems with an enlarged image sizealong with multiple configurableuser fields such as Supplier PartNumberManufacturer Number and soon

Home Screen Available YesNo Enables or disables theHome screenas the entry point for launchingthe catalog The home screendimensions can be enabled in theCustomize Search tab from hierarchyand selection list options

Top Ten Items SuppliersAvailable

YesNo Enables the display of the top tenitems and suppliers

NoteYou must enable Home screen toactivate this option

Expand Sales Package in CartPreview

YesNo Displays the sales packages inexpanded mode in the cartpreview screen

Use Minimum Quantity asDefault

YesNo Ensures that a warning message isissued if the user adds an item tothe shopping cart with an orderquantity less than the minimumorder specified

Show Price Based Quantity YesNo Enables display of Price BasedQuantity values and also the pricebased on Price Based Quantity

Number of Results Numerical entry User defined Allows configuration of thenumber of hits to be displayedafter a search

Use Fixed Table Layout in ListView

YesNo Enables or disables the defaultwidth of list view table If youdisable it you can define the widthof the list view table

Enable Use of Electronic Forms YesNo Enables or disables the electronicforms function that is used tomodify the record data that istransferred to SRM

Display entire hierarchy if founditems less than

Numerical entry User defined Allows the user to specify thenumber of results for which thehierarchy should be displayed

5672 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 57: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

General Tab Search

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM DataManager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

Use Attribute Search YesNo Refines the search for categoriesand suppliers if attributeshave been maintained In theCustomize Search configurationthe hierarchy Category must beselected to enable the AttributeSearch

Use Contract Id Search YesNo Enables or disables the contractId search This refines therecords based on the contract Idinformation

Position of Cart Action in ListView

Numerical input Specifies the position of the cartcolumn in the table

General Tab Compare

Configuration Option Possible Settings Additional Information

Use attribute if priority higherthan

From one to one hundred In SAP NetWeaver MDM Data

Manager you can set prioritiesfor attributes with 1 being thehighest and 100 being the lowest

General Tab Shopping Lists

Configuration Option Possible Settings Additional Information

Shopping Lists Available YesNo Enables or disables you to savea collection of items withoutquantity details which you canuse as a template for future orders

Shopping Lists as Default YesNo Displays Shopping List as the defaultpage when you launch thecatalog

Manage your current ShoppingLists

YesNo Enables or disables you tomaintain your own shopping list

07122010 PUBLIC 5772

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 58: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

Configuration Option Possible Settings Additional Information

Other Shopping Lists Delete YesNo Enables or disables userauthorization for deletingthe Shopping Lists of others

Other Shopping Lists Modify YesNo Enables or disables userauthorization for modifyingthe shopping lists of others

4 Maintain OCI mapping For more information seen Mapping Catalog Fields to Open Catalog (OCI) Fields [external document]n Extending Open Catalog Interface (OCI) Fields [external document]

5 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

332 Configuring the Web Dynpro Search User InterfaceDisplay

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with the parameterltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegt

The following languages are availableChinese (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)

5872 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 59: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

2 Log on to the MDM Server as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Display tabYou can customize the available fields for the following screensn Item Lists

n Shopping Cart Previewn Comparen Item Details

n Context View5 Select one of the above options for example Item List6 In the left frame SRM-MDM Repository Fields select the fields that you want such as Supplier Catalog

Name and Supplier Part Number and choose Add or if you want all fields choose AllThe systemmoves the selected fields to the frame on the right Selected UI Fields This frame displaysthe fields currently displayed in the screen selected in the previous step You can configure theheight and width for Image and Hyperlink fieldsTo change the order of display select the required field in the Selected UI Fields list and use the Upand Down function to change the sequenceTo copy the selected fields to all screens ‒ meaning that all screens display the same fields ‒ usethe Copy To All button

7 You can use the Default Sorting option to specify the column name which enables the sorting ofresults in the item list You can select the required fields from the Selected UI Fields table Thisapplies to the Item List only and the setting is also applied to the context view In this step youalso specify the width for each configured field

8 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

07122010 PUBLIC 5972

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 60: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

333 Configuring the Web Dynpro Search User InterfaceSearch

PrerequisitesYou are assigned the role UI Configuration ManagerThe SAP MDM components of SRM-MDM Catalog 30 are installed and the components are usinga consistent build version

Procedure

1 Start the URL for accessing the configurationUI httpJ2EEserverJ2EEportSRM-MDMSRM MDM

The system opens a logon screen

Note

If you want to use a language other then English call the URL above with parametersltdatalanguagegt and ltsap-localegthttpJ2EEserverJ2EEportSRM-MDMSRM MDMampsap-locale=ltlanguagegtsap-locale

The following languages are availableChinese (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 as describedn Server Name specify the host on which your MDM server is installedn Password specify the server password (if set at all) and choose Connectn Login choose the relevant repository and specify a user name and password

Note

The user must be assigned the role UI Configuration Manager in the MDM Console under Roles

3 Select the configuration options as listed below for the Default User or for each search user whorequires a user-specific configuration

4 Choose Customize Search tab5 Select your preference yes or no for the configuration optionsn Hierarchy and Selection Search in Search Tab

n Show Hierarchy and Selection Search in Advance Search Tab

n Advanced Search in Search Tab

n Advanced Search Tray Expanded6 In Hierarchy choose a field Fields of the type hierarchy or taxonomy are listed here The standard

repository comprises two fields Hierarchy and Category (taxonomy)

6072 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 61: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

Note

To enable the search via attributes you must select the standard delivered field typeCategoryYou can configure the attribute search in General tab

7 Choose the Selection List for example SupplierManufacturer Unit of Measure and so on8 In Advanced Search Fields choose the fields for the Advanced Search You can configure up to

two fields as dropdown lists up to four fields as free form search fields and up to two fields forthe price range search fieldsSAP delivers the following selection of searchable fields as defaultn Supplier Part Numbern Product ID

n Product Groupn Price Information (with Range)n External Manufacturer

9 Choose the corresponding searchable indicator Drop Down Free Form or Range to make the fieldavailable in the Advanced Search

10 To enable a search range for specific fields listed in the Field Name column set the correspondingRange indicator

Note

Only fields with the check box on a white background can be selected

11 Select Operator for each different field type

Caution

Operator contains the most resource-demanding search operator Select with care

12 Choose any one of the followingn To preview the configuration choose Preview Configurationn To save the configuration choose Saven To reset to the default values choose Restore to SAP Default

334 Search Functions in Catalog

You can use this business process to search for items in SRM-MDM Catalog

FeaturesYou can search for items in the catalog using any one of the following search functions

07122010 PUBLIC 6172

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 62: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

n Keyword Search or Advanced SearchYou can access the keyword search and advanced search from the global pane available at the topof all screens of SRM MDM Catalog In Keyword search you can perform a wildcard searchAdvanced Search has three types of searching options as followsl Extended Value Selector (EVS)

This option is available for look up fields in the catalog repository You can trigger a search bychoosing one of the available values in the list If you have configured more than ten values forthe Search field then the EVS search option is enabled by default If you have configured less thanten search values then a drop down is enabled

l Free FormYou can configure the search options you require Some of the search options available arecontains ends with starts with etc You can trigger a search by entering the relevant searchparameters in these fields

l RangeThis option is enabled only for Price fields You can search for a range of values You can enterthe range in From and To

n Category or HierarchyYou can use this feature to search for items using the hierarchy field dimensions defined in thecatalog repository You can access this search option in the Home screen You can also access itthrough the Browse By option

n Selection ListYou can use this feature to search for items based on look up fields The selection list displays allthe available categories and suppliers from which you can select the appropriate category orsupplier to trigger a search You can access this search option in the Home screen You can alsoaccess it through the Browse By option

All these search options are configurable For more information see Configuring the Web Dynpro Search UserInterface Search [page 60]These search options are independent dimensions If you conduct a new search using any one of theseoptions the previous searches are reset You have the option to refine the search results The RefineSearch displays the filtered category and selection list based search You can reset the search performedin Refine Search using the Reset Filter link

335 Mapping Catalog Fields to OCI Fields

To overwrite if necessary the fields that are mapped to the OCI in the standard delivery versionof the SRM-MDM catalogUI Configuration Managers and Administrators use this procedure to

n Change if necessary the system settings for each catalog individually

6272 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 63: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

n To map non-standard fields that is the fields that a customer added to the SRM-MDM repositorysuch as NEW_ITEM-CUSTFIELD1 to OCI fields

Note

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

Delivered OCI Mapping

OCI Field SRM-MDM Field

NEW_ITEM-VENDOR Supplier

NEW-ITEM_ VENDORMAT Supplier PN

NEW-ITEMmdashDESCRIPTION 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 Days

Procedure

1 In the General tab choose OCI Mapping2 In the General tab choose OCI Mapping3 Choose an OCI field and select the SRM-MDM field to which you want to map this field

07122010 PUBLIC 6372

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 64: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

OCI Fields Mappable to SRM-MDMCatalog Fields

n NEW_ITEM-VENDORn NEW_ITEM-VENDORMATn NEW_ITEM-DESCRIPTIONn NEW_ITEM-MATGROUPn NEW_ITEM-MATNRn NEW_ITEM-SERVICEn NEW_ITEM-MANUFACTCODEn NEW_ITEM-MANUFACTMATn NEW_ITEM-LEADTIME

n Suppliern Supplier Catalog Namen Supplier Part Numbern Short Descriptionn Product Groupn Product IDn Categoryn Hierarchyn Service Itemn Price Informationn Contract Pricen Long Descriptionn Special Search Termsn External Manufacturern Manufacturer Part Numbern Standardized Manufacturer Part Numbern Delivery Time in Daysn Unit of Measuren Order Unitn Minimum Quantityn Minimum Quantity UOMn Hyperlinkn Product GUIDn Supplier Item Statusn Item Status

4 Choose Preview Configuration Save or Restore to SAP Default

336 Extending OCI Fields

1 Start the URL for accessing the configuration UIhttpJ2EEserverJ2EEportSRM-MDMSRMMDM

2 In Server Name enter MDM server name and choose Connect3 Select Repository enter user name and password and choose Transport Configuration

Export the configuration and save the configuration XML file to a local drive Start the Editorof your choice to edit the XML file

4 Using the formulation ltfield Name =rdquoNEW_ITEM-ZZ_YOUR_FIELD1rdquogt add your own OCI fieldat the end within the OCI Fields tag

6472 PUBLIC 07122010

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 65: MDM Catalog

3 Catalog Content Management33 Searching in Catalog Data

Figure 3 OCI Fields

5 Save the changed XML file6 Import the changed XML file

337 More Information About Searching in Catalog Data

Run the following system transactions in SAP SRM

n PPOMA_BBP

07122010 PUBLIC 6572

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 66: MDM Catalog

This page is left blank for documentsthat are printed on both sides

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 67: MDM Catalog

A Reference

A Reference

07122010 PUBLIC 6772

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 68: MDM Catalog

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6872 PUBLIC 07122010

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 69: MDM Catalog

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2010 SAP AG All rights reserved

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

07122010 PUBLIC 6972

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 70: MDM Catalog

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides

7072 PUBLIC 07122010

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 71: MDM Catalog

This page is left blank for documentsthat are printed on both sides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 72: MDM Catalog

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2010 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice