SRM-MDM Catalog Implementation – End to End Procedure
Applies to:
Standard SAP MDM 7.1 Console, SAP SRM 7.0, SRM–MDM catalog 3.0 SP11, SRM-MDM catalog content 3.0, MDM SRM UI App. For more information, visit the Master Data Management homepage.
Summary
The main purpose of this article is to show how to integrate SRM-MDM Catalog. A basic step by step guide to implement SRM-MDM Catalog.
Author: Nitish Sharma
Company: Mahindra Satyam
Created on: 21 june 2012
Author Bio
Nitish Sharma has been associated with Mahindra Satyam for 15 months and has been a part of MDM practice. He is skilled in SAP MDM, SAP MDG, SRM MDM, Java, J2EE and completed his Bachelor’s degree in Computer Science.
Table of Contents
1) Background
2) Prerequisites
3) MDM configuration
Creating a mask
Assigning records to mask
4) UI configuration
5) SRM configuration
6) Conclusion
7) Related Content
😎 Copyright
1) Background
System Type | Service | Pack Purpose |
SAP MDM 7.1 Console | 7.1.07.263 | To setup SRMMDM Catalog repository |
SAP SRM 7.0 | SP9 | To setup Catalog ID & call structure |
SRM–MDM catalog 3.0 SP11 | SP11 | Catalog Repository |
SRM-MDM catalog content 3.0 | SRM MDM catalog content deployment | |
MDM SRM UI App | To configure OCI structure & search engine |
Enter all the details to login
Every user is assigned to a repository, select the user as maintained in Webservice.
The Configuration view shows the user specific configuration of SRM MDM Catalog. In the General pane, you can set Shopping options, Item Display Criteria, Search, Shopping Lists and OCI Mapping.
The OCI Mapping is shown in below screenshot.
Here under Customize Display->item lists, we select the fields which we want to deal with on the portal. Just select field and click on add.
For example
Here under Customize Display->Cart preview, we can check the preview of previous step.
Under customize search tab, you can specify that on which fields search can be performed, and what should be the conditions like word “starts with n or m” etc.
For example
Go to transaction SPRO(it requires SRM side authorization first to log in SRM)
Click on SAP Refrence IMG
Click on SAP Implementation->SAP SRM-> SRM Server->Master Data->Content Management-> Define external web services.
Enter the catalog web service id and description for the mask created in SAP MDM
After creating webservice id go to Standard call structure to assign relevant parameters which include repository name (to which catalog belongs), catalog name (mask name).
After assigning all the parameters now we have to assign user id to particular catalog. Go to pposa_bbp tcode. Click on select attribute, then ‘+’ symbol to add user id and catalog
6) Conclusion
With the implementation of above procedure, now we can able to access catalog (mask created in mdm) on the portal, the id created in the last step can only access assigned catalog. The fields which are selected in UI implementation step will be visible in portal. The name of catalog (webservice id) given in webservice under standard call structure will also be visible. So, assigned user can now access the catalog and can make a shopping cart with the items assigned to particular catalog.
© Copyright 2012 SAP AG. All rights reserved.
No 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 be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Oracle Corporation.
JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
9 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |