You use the SRM-MDM Catalog to search, compare, and procure products from suppliers.
It provides:
Catalog content management functions, such as the import of catalog structures or data, the transfer of catalog items to a procurement application, and search functions
Procurement catalogs
Supplier catalogs in a Web-based environment
The SRM-MDM Catalog is based on functions provided by SAP NetWeaver Master Data Management (SAP NetWeaver MDM) and bundles together in one specific application those SAP NetWeaver MDM functions required for catalog content management.
The figure below displays an overview of the SRM-MDM Catalog.
SRM-MDM Catalog: Overview
The following table shows the SAP NetWeaver MDM modules included in the SRM-MDM Catalog:
MDM Server |
MDM Import Manager |
MDM Business Content |
MDM Import Server |
MDM Workflow |
MDM Java API |
MDM Console |
MDM Data Manager |
The search in the catalog repository is integrated with the following SAP SRM and SAP ERP business scenarios:
SAP SRM: Self-Service Procurement
SAP SRM: Service Procurement
SAP SRM: Contract Management
SAP ERP: Purchase Requisition (as of SAP ERP 2005)
SAP ERP: Purchase Order (as of SAP ERP 2005)
SAP ERP: Work Order (SAP Plant Maintenance (SAP PM) / SAP Project System (SAP PS))
Using the MDM Import Manager, you can:
Import data from suppliers such as
Product catalogs
Product hierarchies
The supplier catalogs and product hierarchies can have any format supported by the standard SAP NetWeaver MDM application, such as MS EXCEL, XML, or content from running database systems such as MS SQL, MS ACCESS, or Oracle. The catalog content is compatible with standard classifications such as UNSPSC and eClass.
Import product master data, purchasing contracts, and suppliers from SAP SRM
Import purchasing contracts and purchasing info records from SAP ERP
Upload contract data from SAP SRM 2007 and SAP ERP.
For more information, see Import and Mapping of Catalog Data. The system stores contract prices per catalog item together with the contract ID, the amount, and the contract item category.
Perform a value and key mapping between the supplier's source and the destination structure. Wherever both are in sync, you can auto-map this data. A matching function ensures that no duplicate data occurs.
Using the MDM Data Manager, you can enrich imported data. For example, you can add images and attachments to records, add new items manually, perform a mass change, or reassign records to another category.
Using the MDM Workflow Manager, you have a framework for defining workflows. You can create your own workflow rules to establish role-based workflows using Microsoft Visio 2003 Standard. When designing your workflow, you can use MDM validations and assign the workflow steps to users or roles.
Using the MDM Data Manager, you can determine the necessary parameters for collecting the data for your procurement catalog(s) and making them accessible on the Web. From the procurement application of the supported business scenarios you can open the SRM-MDM Catalog, select catalog items, and transfer the data.
All aspects of the Search UI are configurable to meet user-specific requirements. See User-Specific Configuration for Product Procurement for more details.
SAP Supplier Relationship Management (SAP SRM) provides a BAdI for the OCI outbound process for passing dynamic parameters calculated at runtime. For example, you can pass a parameter that restricts the set of product items the user is allowed to retrieve in a search.
For more information about transferring additional parameters, see Customizing for Supplier Relationship Management (SAP SRM) under
The SRM-MDM Catalog includes a predefined data repository for your catalog data. This standard repository comprises the main table Catalog Items and a number of additional sub-tables, for example, for value lookups or classification.
For more information, see Loading Predefined Repositories for Product Procurement and Extending Predefined Repositories.
The system enables inheritance levels for the supported languages.
Example
US is to be used as the primary language. FR as the secondary language in case US is unavailable. DE substitutes the secondary language if FR is unavailable.
On the other hand, the language of your content (the data language in fields and tables, for example) can be in any language supported by SAP NetWeaver MDM 7.1.
The following table shows the supported languages:
Chinese (ZH) |
Finnish (FI) |
Hungarian (HU) |
Polish (PL) |
Swedish (SV) |
Czech (CS) |
French (FR) |
Italian (IT) |
Portuguese (PT) |
Thai (TH) |
Danish (DA) |
German (DE) |
Japanese (JA) |
Russian (RU) |
Turkish (TR) |
Dutch (NL) |
Greek (EL) |
Korean (KO) |
Slovakian (SK) |
|
English (US) |
Hebrew (HE) |
Norwegian (NO) |
Spanish (ES) |
The SRM-MDM Catalog component uses SAP NetWeaver MDM technology. However, it does not cover the full scope of functions provided by SAP NetWeaver MDM.