SRM-MDM Catalog 1.0: Configuration Guide

Transcription

1 Last revision: April 24, 2007 SRM-MDM Catalog 1.0: Configuration Guide ADDON.SRM_MDM_CATALOG_SC

2 Copyright Copyright 2007 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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 Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. 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. SRM-MDM Catalog 1.0: Configuration Guide 2

3 Icons in Body Text Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library. Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text Example text <Example text> EXAMPLE TEXT Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. SRM-MDM Catalog 1.0: Configuration Guide 3

4 SRM-MDM Catalog 1.0: Configuration Guide... 5 Documentation Landscape for SAP Solutions and Business Scenarios... 7 SAP Notes... 8 System Connections Initializing the SRM-MDM Catalog Repository Setting Up MDM SAP Exchange Infrastructure Configuring the System Landscape Directory Defining Business Systems in the Integration Directory Setting Up Integration Scenarios Creating Communication Channels with Template Interface Determination Process Customizing Restricting the Number of Searchable Catalog Items Setting Up Masks for Searching the Catalog Repository Setting Up Named Searches Setting up External Web Services in SRM Making the Catalog Web Service Available in the Organizational Plan Configuring the Search in the Web Dynpro UI Mapping Catalog Fields to OCI Fields Setting Up Contract Replication Setting Up the Key Mapping for Contract Item Categories Implementing BAdI to Enrich Contract Data Configuring Role for Data Import via Import Server SRM-MDM Catalog 1.0: Configuration Guide 4

5 SRM-MDM Catalog 1.0: Configuration Guide This business scenario configuration guide applies to the SRM-MDM Catalog 1.0 business scenario with the corresponding releases of its SAP application components. Business Scenario and Application Components Business Scenario Application Component with Minimum Release SRM-MDM Catalog SAP SRM-MDM Catalog 1.0, including the following MDM 5.5 SP4 components: MDM Server MDM Import Server MDM Console MDM Import Manager MDM Workflow MDM Data Manager SAP SRM Server (any Release) SAP Exchange Infrastructure optional (Release depending on SAP SRM Server version) mysap ERP 2005 optional Make sure to observe the following dependence between SRM and XI content: SRM Server Release XI Content Version Predelivered XI Content 6.0 [SRM 6.0] XI Content 7.0 (with NetWeaver Basis 2004s) 5.5 [SRM 5.0} XI Content 7.0 (with NetWeaver Basis 2004s) 5.0 [SRM 4.0} XI Content 3.0 (with NetWeaver Basis 2004s) Yes Yes No EBP 3.5 XI Content 2.0 No Regarding the question which patch level for PI and PI Basis is relevant to your setup, refer to SAP Note SRM-MDM Catalog 1.0: Configuration Guide 5

6 File System Catalog Manager Import Manager + Console Catalog Admin. / Config.Manager * SRM-MDM Catalog Data Manager Config UI Catalog User Search UI SAP XI Catalog User / * Administrator mysap SRM mysap ERP Product hierarchy Map import data to catalog repository Import product hierarchy *Define masks, named searches and validations * Configure search UI Enable Web content * Set up Web service Transfer info records and contracts from ERP Catalog files in various formats Import catalog data Contracts and info records from ERP Contracts and products from SRM Auto-import contracts + info records from ERP Auto-import contracts and products from SRM Enrich product data Approve product data XML mapping/ routing XML mapping/ routing Transfer product data from SRM Transfer contract data from SRM Assign products to mask (required if you use masks) Search for products in catalog repository Transfer items to procurement system Launch catalog search via URL Continue with procurement activity SRM-MDM Catalog: Component View Contents The business scenario configuration guide contains all steps required to implement the SRM- MDM Catalog business scenario. The guide specifies the sequence of the configuration activities, and their dependencies. It includes information about the following topics: System Connections Business Customizing For more information about the SRM-MDM Catalog business scenario, see SAP Service Marketplace at service.sap.com/ibc-srm.. Target group Technical consultants SRM-MDM Catalog 1.0: Configuration Guide 6

7 Application consultants Project team members during the implementation of an SAP solution SAP customer IT department The System Connections section is aimed at technical consultants in particular. The remaining sections are of equal interest to both groups of consultants. The importance of sections to the other target groups depends on their responsibilities. It is a prerequisite that consultants have completed all relevant training courses before starting to work with this guide. Integration Documentation Landscape for SAP Solutions and Business Scenarios The system landscape has already been created using the Master Guide and other documentation. For more information about other relevant documentation. See Documentation Landscape for SAP Solutions and Business Scenarios [Page 7] Business Scenario Configuration Guide Feedback Your feedback can help us to continually improve the business scenario configuration guide. If you find errors in the configuration guide, create a message in the SRM-KM-DOC component in SAP Service Marketplace at service.sap.com/message. Documentation Landscape for SAP Solutions and Business Scenarios Purpose This documentation gives you an overview of the major sources of information available to you on SAP solutions and business scenarios. Always use the current documents in your implementation. Current Documents Document Master Guide, Installation and Upgrade Guides Business-Scenario Configuration Guide Implementation Guide (IMG) Business Scenario Description SAP Library Quick Link on the SAP Service Marketplace (service.sap.com) instguides ibc ibc Note: This is in the SAP system, not in SAP Service Marketplace ibc The following information supplements the individual documents: helpportal with all releases of a SAP component Note: Available in the SAP system under Help SAP Library SRM-MDM Catalog 1.0: Configuration Guide 7

8 Current Supplementary Information Information SAP notes Technical infrastructure (for example hardware sizing, platforms, network security) Quick Link on the SAP Service Marketplace (service.sap.com) notes for the note search instguides listed by installation and upgrade guide ti Features The following documents are available for a SAP solution. Master Guide, Installation and Upgrade Guides These documents describe how you install or upgrade the system landscape required by a business scenario. The central initial access document for each SAP solution is the Master Guide. It lists the SAP application components and third-party applications required by each business scenario, and refers to their installation and upgrade guides. These are component installation guides, business scenario upgrade guides, and component upgrade guides. Business-Scenario Configuration Guide This document describes the settings you use to configure the SAP application components and third-party applications required for a business scenario. It contains information specific to business scenarios for the particular IMG activity. It does not reiterate the IMG documentation but makes reference to particular IMG texts. Implementation Guide (IMG) This tool adjusts SAP systems to customer requirements. The IMG contains the IMG activities for all SAP components, and general documentation. The structure is component-oriented, without reference to a business scenario. The Business-Scenario Configuration Guide establishes the link between the IMG and the various business scenarios. Business Scenario Description This document describes how a business scenario runs once all components have been installed and configured. All the business processes of a business scenario are represented graphically in the component view, which illustrates the process steps of each SAP component. SAP Library This contains the entire documentation of SAP components and business scenarios. The Business Scenario description is part of the SAP Library. SAP Notes Definition This section lists all SAP Notes that are relevant to this business scenario. Ensure that you read the information contained in the Release Information Note (RIN) for the current support package, as listed in the table below. SRM-MDM Catalog 1.0: Configuration Guide 8

9 SAP Notes Note Number Title Support Package 00 for SRM Release 4.0 (RIN) XI 2.0 (SP1 and higher): Importing XI Content SRM 4.0 SP stack 08/2004: Release and information note (RIN) XI 3.0 (Support Package 1 and higher): Importing XI Content SRM 4.0 SP stack 09/2004: Release and information note (RIN) SRM 4.0 SP-Stack 10/2004 (SAPKIBKS03): Release and Informat. (RIN) SRM 4.0 Support Release SRM 4.0 SP-Stack 03/2005 (SAPKIBKS05): Release and Informat. (RIN) SRM 4.0 SP-Stack 12/2005 (SAPKIBKS08): Release Information SRM 4.0 SP-Stack 06/2005 (SAPKIBKS06): Release and Informat SRM 5.0 SP-Stack 01 (10/2005): Release Information Note SRM 5.0 SP-Stack 02 (12/2005) (SAPKIBKT02): Release/Info Note SRM 5.0 SP-Stack 03 (02/2006) (SAPKIBKT03): Release/Info Note SRM 5.0 SP-Stack 04 (04/2006) (SAPKIBKT04) SRM 4.0 SP-Stack 04/2006 (SAPKIBKS09): Release Information SRM 5.0 SP-Stack 05 (07/2006) (SAPKIBKT05): Release/Info Note MDM 5.5: Generic extractor for Customizing data SRM-MDM Catalog 1.0 SRM-MDM Catalog 1.0: Configuration Guide 9

10 Installation & Configuration SRM-MDM Catalog 1.0 Patch01 Release Note Purpose System Connections This section contains information about connecting the systems in a SAP system landscape. This involves, for example: Determining the systems, servers, clients and other components, in the system in which the SAP application component is installed Completing the configuration settings and performing other activities required for the interactions in a SAP system landscape Prerequisites You have applied SAP Note and the related notes. Use Initializing the SRM-MDM Catalog Repository In this procedure you configure the generic Extraction Framework and the FTP file transfer for the SRM-MDM Catalog in order to initialize your catalog repository. In detail, the procedure includes the following tasks: Configure the Extraction Framework Upload the configuration by means of a configuration file and a report Check the upload result in the SAP client system Set the home directory for the FTP server Replicate mysap SRM or my SAP ERP customizing data to the SRM-MDM Catalog repository In this task you replicate such data as currencies, units of measure, product groups and purchasing organizations into SAP MDM. You replicate purchasing organizations from mysap ERP only. Check the replication result in one of the following SAP MDM applications: MDM Import Manager MDM Data Manager Prerequisites You have implemented SAP Note in your mysap SRM or msap ERP system. You have downloaded the configuration file MDMGX_Catalog.txt to your local drive. SRM-MDM Catalog 1.0: Configuration Guide 10

11 You find the file MDMGX_Catalog.txt in the attachments of SAP Note Before replicating the customizing data or before checking the replication, you have started the MDM Server and MDM Import Server, and you have loaded the SRM-MDM Catalog repository. Configuring the Generic Extraction Framework 1. Logon to your mysap SRM client or mysap ERP client system using the SAP GUI Logon. 2. Start transaction SE38. a. Enter the report name MDM_GX_UPLOAD_MDMGXC1. b. Start the report. 3. On the initial report screen perform the following steps: a. Select Catalog as Object Type. b. Select the downloaded file MDMGX_Catalog.txt from your local drive. c. Make sure that the Remove Header Line checkbox is selected. d. Execute the report. Checking the Upload Result on the SAP Client System 4. Start transaction MDMGX in the SAP client system (mysap SRM or my SAP ERP). a. Select the Maintain Ports and Check-Tables menu item. The system opens a selection screen. b. Select Catalog as Object Type. You can click the field and use the input help (F4). c. Choose Execute. The system displays an overview of customizing tables and their assignment to MDM port codes. 5. Review the table content. Verify that there are entries for the relevant system types (R3 and SRM). Setting the Home Directory for the FTP Server Set the home directory of your FTP server to the following path: <SAP MDM 5.5 installation directory>\server\distributions Replace <SAP MDM 5.5 installation directory> with the directory name of your MDM Server installation. If you have changed the Distribution Root Dir setting in the mds.ini file (configuration file) of the MDM Server, you need to set the home directory accordingly. Replicating Customizing Data of mysap SRM or ERP to Repository 6. Start transaction MDMGX (unless already running) on the SAP client system (mysap SRM or my SAP ERP). SRM-MDM Catalog 1.0: Configuration Guide 11

12 7. Choose Define Repositories and FTP Servers. a. Change to Edit mode. b. Select the SAP_SP4_PRODUCT repository template and choose Copy As... The system opens a screen to enter the repository and FTP details. 8. Enter a name for the Logical Repository and change the following settings as required: Object Type Using the input help, select Catalog. Repository Name (Code) It must be identical to the SRM-MDM Catalog repository name in SAP MDM. FTP Server URL to your FTP server that contains the port folder structure MDM Root Root folder of your local port folder structure Client Code Refers to the system client Client System Type The entries R3 and SRM represent the mysap SRM and my SAP ERP client systems. Languages The SRM-MDM Catalog repository supports the languages EN, FR, DE. Timeout (Minutes) 9. Save your changes and return to the MDM 5.5 Generic Extractor main screen. For more information about replicating configuration data, see the How to Load Reference Data with SRM-MDM Catalog guide at service.sap.com/srm mysap SRM in Detail <Release> Procurement Catalog Content Management. 10. Choose Start Extraction. The system opens a screen to enter extraction parameters. a. Select the <SRM-MDM Catalog> repository. You use the repository name you have entered in step 3. The system automatically adds the data you have configured in step 3 such as Address of FTP Server. b. Set the FTP_DWNL indicator to activate the FTP download. c. Optional: Set the FTP_DWNL indicator to activate the FTP download and specify a local directory in the FIL_DIR field. d. Choose Execute. Checking the Replication Result in SAP MDM Perform the following steps in one of the following SAP MDM applications: MDM Import Manager Select Port as Type of the data source. MDM Data Manager Open the following lookup tables and SRM-MDM Catalog 1.0: Configuration Guide 12

13 Setting up a Repository Structure Adapting Repository Templates for SAP Client Systems Setting Up MDM Ports SAP Online Help Select the relevant client system (mysap SRM or my SAP ERP). Open the Ports drop down list and check whether the following ports are available (have been processed successfully) LT_Currencies LT_ProductGroups check their entries: Product Groups Currencies UoM ISO Code Purchasing Organizations (only mysap ERP) LT_UOM_ISO_Code LT_PurchasingOrganization (only mysap ERP) and no exception occurred. You can select a lookup table via dropdown box in the upper left pane of the MDM Data Manager. Purpose Setting Up MDM This section refers you to the IT Scenario Configuration Guide for SAP NetWeaver MDM 5.5 (Document Version 2.00 September 2006) available on the SAP Service Marketplace via quick link operationw04 SAP MDM SAP MDM 5.5 Documentation Center MDM 5.5 SP04 - IT Scenario Configuration Guide. For the SRM-MDM Catalog scenario you need to consider the sections outlined below: Procedure 11. If you need to adjust a shipped repository template, refer to the following sections: Setting up a Repository Structure Adapting Repository Templates for SAP Client Systems 12. To make your client systems known to MDM, you need to consider these sections: Setting up Connection Information Defining Client Systems and Key Generation Setting Up MDM Ports 1. To provide the check tables in MDM as reference data, you need to consider these sections: Loading Reference Data Cross-System Repositories: Importing Automatically 1. If you use SAP XI, refer to the section Setting up XI. Make sure to observe also the section SAP Exchange Infrastructure of the SRM- MDM Catalog configuration guide. SRM-MDM Catalog 1.0: Configuration Guide 13

14 Purpose SAP Exchange Infrastructure In this section, you make settings in SAP Exchange Infrastructure (SAP XI) that are required for the SRM-MDM Catalog 1.0 business scenario. These settings enable you to upload data using SAP XI and enable SRM Server and SRM-MDM Catalog to communicate with each other using the Integration Server. You do not need SAP XI in the following circumstances: You only want to provide supplier catalogs in a Web-based environment. You do not replicate product or contract data. You need the SAP Exchange Infrastructure for the following data exchanges between SRM or ERP and the SRM-MDM Catalog system: Contract replication (upload from SRM to the SRM-MDM repository) Product data replication from SRM Replication of info records with material master data and contracts from ERP If you use SAP XI, also refer to the section Setting up XI of the MDM 5.5 SP04 - IT Scenario Configuration Guide. Prerequisites We strongly recommend that you use an Integration Scenario (and preferably the top down approach) since this will simplify the configuration very much by means of semi-automatic (wizard-driven) procedures. If you are not familiar with the communication scenarios of Process Integration (PI), demo examples are available to demonstrate the technical concepts and tools step-by-step. See help.sap.com SAP NetWeaver SAP NetWeaver 2004s SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Overview Examples. You have set up and configured a system connection between SRM Server and SAP XI (for the exchange of messages with the Exchange Infrastructure and the Integration Server by using ABAP proxies). You have installed the Integration Server. For more information, see SAP Service Marketplace at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 2004s Installation. You have installed the SAP components that are relevant for the SRM-MDM Catalog 1.0 business scenario. For more information, see SAP Note You have imported the SAP XI content for SRM Server and for SRM-MDM Catalog 1.0. The SAP XI content for SRM-MDM Catalog 1.0 is not part of the standard SRM Server XI content. See also: SRM-MDM Catalog 1.0: Configuration Guide 14

15 SAP Notes : XI 2.0 (SP1 and higher): Importing XI Content : XI 3.0 (Support Package 1 and higher): Importing XI Content SAP Service Marketplace at service.sap.com/ibc-srm Master Guide for mysap SRM. Use Configuring the System Landscape Directory To use SAP Exchange Infrastructure as part of the SRM-MDM Catalog 1.0 business scenario, you must define the following in the System Landscape Directory (SLD): The systems that use SAP Exchange Infrastructure to send messages: SRM Server The systems that receive messages from SAP Exchange Infrastructure: SAP MDM Server In this section, you define the system landscape in the SLD. The graphic below shows a possible system landscape for the SRM-MDM Catalog business scenario. The graphic also shows the required system connections and protocols, and the processes for which those system connections and protocols are required. The bold lines represent connections that are always required. The arrows show the direction of the requests. SRM-MDM Catalog 1.0: Configuration Guide 15

16 Web Browser & Client File System Plain HTTP(S) SAP MDM Catalog Client Components SAP MDM Console SAP MDM Data Manager SAP MDM Import Manager Server Components SAP MDM Server * SAP MDM Import Server Internal MDM protocol SAP Web AS Java MDM Connector SRM-MDM Admin UI SRM-MDM Search UI HTTP(S); includes OCI communication (3) SRM Server Integration Engine (1) FTP(S) (2b) XI protocol (2a) Server File System Supplier Catalogs File adaptor XI Integration Server Numbered connections and corresponding processes: (1) Upload of supplier catalogs via Server File System to SAP MDM Catalog, for example in XML format. (2 a+b) Replication of product and contract data. You use the integration scenario SRM_MDM_Catalog. (3) OCI communication when starting the URL to search the catalog repository. Procedure Configure the technical and business system landscape for the following installed components: SRM Server (Role: Application System) Integration Server (Role: Integration Server) SAP SRM-MDM Catalog (Role: Application System) For information about configuring the technical and business system landscape, see the documentation in the following table: Subject Title of Documentation Path in the SAP Help Portal Configuring the technical system landscape for 3rd Party Applications (Non- ABAP / Non-Java Systems) Technical System Landscape (System Landscape Directory) (At help.sap.com ) SAP NetWeaver Release 2004s SAP NetWeaver Library Administrator s Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems Process Integration (PI) SRM-MDM Catalog 1.0: Configuration Guide 16

17 Configuring the business system landscape (Registering an External System as a Business System) Configuring Integration Scenarios Result Configuring a Business System Business Solution Configuration You have now defined business systems for each of the installed components. SAP NetWeaver SAP NetWeaver 2004s SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Design and Configuration Time Configuration System Landscape Directory in SAP Exchange Infrastructure SAP NetWeaver SAP NetWeaver 2004s SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Enabling Application-to-Application Processes Core Development Tasks Defining Business Systems in the Integration Directory Use In this section, you define the technical communication parameters between the Integration Server and the SRM-MDM Catalog business system you configured in the System Landscape Directory. Prerequisites In the System Landscape Directory, you have defined the business systems that you want to use. You have imported SAP XI content for the SRM-MDM Catalog (as part of the installation process). The Checklist: Developing XI Content in the Integration Repository can assist you in your activities. See help.sap.com SAP NetWeaver SAP NetWeaver 2004s IT Scenarios at a Glance Enabling Application-to- Application Processes Reference. SRM-MDM Catalog 1.0: Configuration Guide 17

18 ... SAP Online Help Procedure... Define the business systems that you are using in the Integration Builder as described in section Importing Integration Scenarios. 1. In the Assign Party step, do not make an entry in the Party field. 2. In the Select Business System step: a. Choose the Business System for the SRM-MDM catalog. b. Make sure to deselect the indicator Create Communication Channels Automatically. Use Setting Up Integration Scenarios In this section, you can import the predefined SRM-MDM Catalog integration scenario from the Integration Repository and generate the corresponding Configuration Scenario. If you do this, you do not need to define receiver routing and interface routing manually. You can use the following integration scenario for the SRM-MDM Catalog: SRM_MDM_Catalog This integration scenario is contained in the namespace MDMCatalog. Prerequisites You have configured the System Landscape Directory (SLD). Procedure 1. Start SAP Integration Builder by choosing Integration Builder: Configuration. 2. Choose Tools Transfer Integration Scenario from Integration Repository. 3. Select the predefined SRM_MDM_Catalog integration scenario and assign the (customer-specific) name you want to use for your scenario <my_srm- MDM_catalog_scenario>. The integration scenario configurator (wizard) opens automatically. 4. Follow the configuration steps in the left-hand frame of the integration scenario configurator: a. Select the component view SRM_MDM_Catalog. b. Under Assign Services select the relevant business systems: The business system for SRM-MDM Catalog The business system for SRM or ERP. c. Configure Connections Ensure that you do the following: Create a receiver channel with the adapter type XI for each connection. SRM-MDM Catalog 1.0: Configuration Guide 18

19 ... SAP Online Help For further details, refer to the section Creating Communication Channels with Template. Set the Generation indicator in the Create Configuration Objects dialog box. Set the Receiver Determination, Interface Determination, and Sender/Receiver Agreement indicators in the Create Configuration Objects dialog box For more information, see section Interface Determination. Once you have completed the steps in the integration scenario configurator, the system displays a results list. 5. Check whether the results list contains any errors. For more information about defining and configuring scenarios, see the SAP Help Portal at help.sap.com SAP NetWeaver SAP NetWeaver 2004s SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Design and Configuration Time. Use Creating Communication Channels with Template To set up the connections between two actions on your component view (that is, the details related to the line between two rectangles), XI uses Communication Channel Templates. You generate them in the wizard step Configure Connections. Procedure 1. Navigate to the empty field Communication Channel and choose option Create Communication Channel with Template. A wizard-driven dialog opens. 2. Choose Step Select Template and follow the procedure as prompted by the wizard, using the Continue and Finish functions. The wizard automatically fills the relevant fields. 3. Choose Step Create New Communication Channel and follow the wizard until finished. 4. Repeat this procedure for all your connections in the Component View. The Integration Scenario includes actions for the upload of products and contracts originating either from SRM or ERP. You generate the Communication Channels that are relevant for you either with respect to SRM or ERP. 5. Once you have created the relevant connections, for the FTP upload, you need to specify attributes such as File Access Parameters or FTP Connection Parameters. Use Interface Determination To make sure the upload of contract and product data uses the adequate interfaces, you need to edit the Interface Determination. You do this in the Integration Directory for the scenario <my_srm-mdm_catalog_scenario> that you specified above in the section Importing Integration Scenarios. Procedure 6. In the SAP Exchange Infrastructure Tools start the Integration Directory (Integration Builder: Configuration). Select your catalog scenario and expand the sublevels. SRM-MDM Catalog 1.0: Configuration Guide 19

20 7. Open the node Interface Determination. There you find inbound interfaces, three of them dealing with contracts, one with products: Interface Used for: MDMContractDataTransmission4ProductID_In Contract items containing a product ID. MDMContractDataTransmission4ProductCategory_In MDMContractDataTransmission4SupplierPartNumber_In MDMProductDataTransmission_In Contract items containing a product category. Contract items containing a Supplier Part Number. Transmitted product data. If a transmitted record includes several types of content (as stated above in the Used for column), the system routes this data to several interfaces. 8. Make sure to choose Standard as the type of Interface Determination and to deselect the Maintain Order At Runtime indicator. 9. For each of the above interfaces you need to configure a Condition. a. Navigate into the empty Condition field. The Condition Editor opens. b. For the first Interface you are setting up, you need to specify the Namespace < and the corresponding namespace Prefix nr1. c. Set up the Xpath expression for the condition using the expression editor: Click a line to open the expression editor. Each line of the condition editor represents one operand of the condition. You can combine two operands using the following Boolean operators: represents AND The system indicates an AND-condition by putting a bracket in front of the two connected lines. represents OR represents NOT For further details regarding the exact formulation of the Xpath expression refer to SAP Note Process Customizing In this section, you make different settings to control your catalog process. They are located in the following places: In MDM, such as settings up masks in the MDM Data Manager In the SRM-MDM application, such as the setting to configure the search UI In the Implementation Guide of SRM, such as setting up the Web Service(s) for your catalog(s) SRM-MDM Catalog 1.0: Configuration Guide 20

21 ... SAP Online Help Restricting the Number of Searchable Catalog Items This section includes the settings that are relevant to reduce the number of catalog items to be available in a catalog search. To constrain the number of searchable catalog items, you can use the following alternatives for your catalog Web services: Setting up Masks for Searching the Catalog Repository [Page 21] Setting up Named Searches [Page 22] Setting Up Masks for Searching the Catalog Repository Use To restrict the number of search items that a user can retrieve when running a search in the SRM-MDM Catalog, the catalog manager or the administrator can specify masks in the SAP MDM Data Manager, assign products to the mask, and assign the mask to roles or users. You have the following options to restrict the catalog access using masks: In the SRM customizing of the catalog Web service, you can specify existing masks. Per Web service you can specify one mask and one user. See section Setting up External Web Services in SRM [Page 23] In MDM Console, you can specify constraints for the Masks table. To do this, you navigate via Admin Roles, you select the Tables and Fields tab, and under Masks, you select one or more values in the Constraints column. Settings you make using the MDM Console option have higher priority and overrule the mask setting in the SRM Web service. In the URL to open the search UI of the SRM-MDM catalog, the mask and user parameters are independent from each other. However, in the search UI, you can also use the mask parameter to restrict the scope of products available in the search result. Procedure 1. In SAP MDM Data Manager, create a mask. 2. Run a search and create a result set of the products you want to group in the mask. 3. Select the relevant products and choose Add to Mask. 4. To adjust an existing mask, you can Replace or Remove products from the mask. 5. To update several masks at a time, in the Records menu, choose Modify Mask. You can modify the mask and add a search selection to the mask. 6. In the SRM customizing of the catalog Web service, you can specify a mask for accessing the catalog. You can also pass the parameter mask dynamically using a Business Add-In. See path in the Implementation Guide (IMG): Supplier Relationship Management SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs, Vendor Lists etc.) Transfer Additional Parameters. SRM-MDM Catalog 1.0: Configuration Guide 21

22 ... SAP Online Help Result You have set up a search constraint that you can apply to a runtime search to limit the initial set of catalog item records in the search result. Use Setting Up Named Searches To reduce the number of searchable catalog items, you can use the Named Searches function of SAP MDM. You can create named searches in MDM Data Manager and use them as an alternative to masks. You can apply a named search by means of the namedsearch parameter in the configuration of your catalog Web services. See Setting up External Web Services in SRM [Page 23] You can also pass the namedsearch parameter dynamically using a Business Add-In. See path in the Implementation Guide (IMG): Supplier Relationship Management SRM Server Business Add-Ins (BAdIs) External Web Services (Catalogs, Vendor Lists etc.) Transfer Additional Parameters. Prerequisites In SAP MDM Console you have created a Named Searches lookup table (flat or hierarchical). When adding this table, you need to use the Table Type Named Searches. The system overwrites the table name you have entered and changes it to Named Searches. In SAP MDM Data Manager you have added Named Searches with relevant names and assigned them to the Named Searches lookup table. Procedure You can specify any name, for example, a name that refers to a user group (such as Catalog for managers). You can assign authorizations for users who are allowed to create or change Named Searches. For more information about Saving and Restoring Named Searches, see the MDM 5.5. Data Manager Reference Guide, available at service.sap.com/nw04operation SAP MDM. 1. Open the MDM Data Manager and change to Record mode. 2. Run a search and create a search result. 3. Open the Search menu, 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. Result You have set up a search constraint that you can apply to a runtime search to limit the initial set of catalog item records in the search result. SRM-MDM Catalog 1.0: Configuration Guide 22

23 ... SAP Online Help Use Setting up External Web Services in SRM To use the SRM-MDM Catalog with SAP SRM and to access the SRM-MDM Catalog via URL from SRM applications, you must specify a corresponding Web Service. You do this in Customizing for Supplier Relationship Management by navigating in the SAP Implementation Guide (IMG) to: SRM Server Master Data Define External Web Services (Catalogs, Vendor Lists etc.). Procedure If you need multiple URLs to access the catalog, you need to set up a corresponding number of Web services as outlined below. 1. In the IMG activity Define External Web Services (Catalogs, Vendor Lists etc.), create a Web service with an ID that refers to your catalog, for example, SRM-MDM-Catalog. a. If you want to assign the catalog to a particular purchasing organization, enter the organization in the Purch. Organization field. b. Under Additional Functions in the Product Catalog, set the following indicators: Display Product Data Again in Catalog Enables using the Detail feature for the OCI. Only with this setting the Detail action ( glasses symbol) in the overview list of catalog items opens product details. Cross-Catalog Search Enables the selected catalog to be searched by a keyword search that expands over all catalog Web services having this indicator. 2. In the navigation tree of the customizing transaction, double-click Integrated Call Structure. It is possible to define a standard call structure for your catalogs instead. However, we do not recommend this, as these catalogs are intended to be displayed as integrated catalogs. The system opens a maintenance screen where you need to maintain the following parameters. Note the information in the Remark column. Parameter Parameter Value Type Remark Name Use the following syntax: MDM/SRM_MDM URL username <your_user_name> Fixed Value <J2EEserver> is the host on which the J2EE server is installed <J2EEport>is the http port of the J2EE server. The value can be that of any user maintained for the catalog SRM-MDM Catalog 1.0: Configuration Guide 23

24 Refers to the user in SAP MDM (not the end user starting the catalog search in SRM). password <your_password> Fixed Value server <your_mdm_server> Fixed Value catalog SRM_MDM_CATALOG Fixed Value port For example: <2000> Fixed Value uilanguage SY-LANGU SAP- Field datalanguage For example: <EN> Fixed Value mask <your_mask_name> Fixed Value HOOK_URL Return URL ~target _top Fixed Value ~caller CTLG Fixed Value ~OKCode ADDI Fixed Value repository in SAP MDM Console under Admin Users. Host on which your MDM server is installed. The name of the catalog repository in SAP MDM. The value must be identical to the port that is assigned to your catalog repository in SAP MDM Console. The system uses the logon language (the initial release supports German/English/ French). This setting can be used to reflect the locale of a language such as EN-US (for American English). If you do not specify a mask, all users have the same unrestricted access to the catalog. SRM-MDM Catalog 1.0: Configuration Guide 24

25 SAP Online Help Making the Catalog Web Service Available in the Organizational Plan Use To enable users of your organizational plan to access the catalog web service, you need to configure the parameter Catalog ID in the Organizational Management. Procedure 1. Navigate to the following activity in the Implementation Guide (IMG) for Supplier Relationship Management: SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan (Transaction PPOMA_BBP). 2. Select an organizational unit, for example, a Purchasing Unit. 3. Open the Attributes tab and fill the value for parameter Catalog ID with the Web service ID that you created in section Setting up External Web Services in SRM. You can assign the parameter on top level so that all users inherit this setting and can thus use the web service. Or, you can assign the parameter on a lower level and enable access, for example, only for specific users on a position level. If you do not add the Catalog ID to the attributes for the organizational unit to which the user of the SRM-MDM catalog is assigned, the catalog will not be available for this user in the SRM system. Use Configuring the Search in the Web Dynpro UI As the owner of the role UI Configuration Manager, you can configure the Java-based (Web Dynpro) search user interface of the SRM-MDM Catalog for the application levels Shopping Cart and Shopping Cart Preview. With regard to search users and user groups (known to the SAP MDM system) you can specify general settings for the result set, the hierarchical search, the selection list and customize which fields are to be available in the search and display screens. In the standard, a configuration is assigned to the Default user. You can assign it to any user available in the catalog repository in MDM Console. You can preview the configuration and save it as a user-specific default. You can restore this configuration and, you can restore the configuration settings initially delivered by SAP. On the configuration screen you also perform the OCI Mapping. For more information, see Mapping Catalog Fields to OCI Fields [Page 28]. Prerequisites You have installed the SAP MDM components of SRM-MDM Catalog 1.0 and made sure that they use a consistent Build version. Procedure 1. Start the URL for accessing the configuration UI: SRM-MDM Catalog 1.0: Configuration Guide 25

26 /tc~mdmsrmui/mdm_srm_ui_app The system opens a logon screen. 2. Log on to the MDM Server by entering the following data: a. Under Server Name, specify the host on which your MDM server is installed and choose Connect. b. Under Login, choose the relevant repository and specify a user name and password. The user must have the role UI Configuration Manager assigned, as specified in MDM Console under Roles. 3. Select one of the following Shopping Options: Shopping Cart As a result of this setting, the system does not offer a Shopping Cart Preview before transferring items to the shopping cart application. Shopping Cart Preview. This setting enables the possibility of displaying a preview of the shopping cart before transferring items to the shopping cart application. 4. Under User-Specific Configuration, configure the following for a user or user group: General Settings for the Result Set You can set up a tree view (taxonomy) or a list view structure as the default setting. You can specify the maximum number of items in the search result for which the system will always use the list view. i. Choose the General tab. ii. Under Item Display Criteria select on of the options, for example: List view. iii. To limit the number of items to be shown in list view, enter a value in the Results Less Than field. Customized Display You can select the available fields for the following screens: Result Set Shopping Cart Preview Compare Item Details iv. Choose the Customize Display tab. v. Select one of the above options, for example: Result Set. vi. To enable the display of fields, select some (or all) of them in the left frame and choose Add (or All). The system moves the selected fields to the frame on the right which contains all fields currently to be displayed. vii. Using the Up and Down function, you can change the sort order of the fields. Settings for the Hierarchical Search SRM-MDM Catalog 1.0: Configuration Guide 26

27 You can configure which kind of field the system is to use for the search, for example: Hierarchy Category (Taxonomy) viii. Choose the Customize Display tab. ix. From the Hierarchy drop-down box, select one of the available options, for example: Category. If you want to enable the search via attributes, you need to select the Category option. Settings for the Selection List You can configure which field the system is to use for the search, for example: Suppliers Manufacturers x. Choose the Customize Display tab. xi. From the Selection List drop-down box, select one of the available options, for example: Category. Search fields of the Advanced Search You can select the relevant fields to be available as search criteria and specify which ones are to have a range. As default, SAP delivers the following selection of searchable fields: Supplier Part Number Product ID Product Group Price Information (with Range) External Manufacturer xii. Choose the Customize Display tab. xiii. To enable a field listed in the Field Name column for the Advanced Search, set the corresponding Searchable indicator. xiv. To enable a search range for specific fields listed in the Field Name column, set the corresponding Range indicator. Only fields with the check box on a white background can be selected. 5. To preview the configuration settings you have made, choose Preview Configuration. 6. To save the configuration settings you have made, choose Save. 7. To save the configuration settings as user-specific default, choose Set as Default. To reset changes done to this default configuration, choose Restore Default. 8. To reset the configuration to the settings delivered by SAP, choose Restore to SAP Default. SRM-MDM Catalog 1.0: Configuration Guide 27

28 Use Mapping Catalog Fields to OCI Fields In the standard delivery version of SRM-MDM Catalog, the standard fields are already mapped to fields of the Open Catalog Interface (OCI). UI Configuration Managers and Administrators can use this procedure to change these standard settings for each catalog repository individually, and to map non-standard fields (the ones a customer added to the SRM-MDM repository) to OCI fields. You can map OCI fields for the following applications: Shopping Cart Shopping Cart Preview SRM-MDM Catalog 1.0: Configuration Guide 28

29 You Can Map Each of the Following OCI fields NEW_ITEM-VENDOR NEW_ITEM-VENDORMAT NEW_ITEM-DESCRIPTION NEW_ITEM-MATGROUP NEW_ITEM-MATNR NEW_ITEM-SERVICE NEW_ITEM-MANUFACTCODE NEW_ITEM-MANUFACTMAT NEW_ITEM-LEADTIME to a Corresponding Field Within the set of SRM-MDM Catalog Fields: Supplier Supplier Catalog Name Supplier Part Number Short Description Product Group Product ID Category Hierarchy Service Item Price Information Contract Price The default mapping that is delivered with the application is shown in the following graphic: Long Description Special Search Terms External Manufacturer Manufacturer Part Number Standardized Manufacturer Part Number Delivery Time in Days Unit of Measure Order Unit Minimum Quantity Minimum Quantity UOM Choosing the function Restore to SAP Default will reset the OCI mapping to these settings. Hyperlink Product GUID Supplier Item Status Item Status There are a number of pre-mapped (hard-coded) fields, which you cannot change: OCI Field SRM-MDM Field NEW_ITEM-PRICE Price Amount NEW-ITEM_CURRENCY Price Currency SRM-MDM Catalog 1.0: Configuration Guide 29

30 ... SAP Online Help NEW-ITEM_PRICEUNIT NEW_ITEM-UNIT NEW_ITEM-PURCHORG NEW_ITEM-PURCHINFREC NEW_ITEM-CONTRACT NEW_ITEM-CONTRACT_ITEM NEW-ITEM_ATTACHMENT NEW-ITEM_ATTACHMENT_TITLE Price Base Quantity UOM Price Base Quantity Purchasing Organization Purchasing Info Record ID Contract ID Contract Item ID URL URL Description Moreover, the OCI provides several customer fields that are not used in the standard version of the SRM-MDM Catalog, for example NEW_ITEM-CUSTFIELD1. Procedure 1. Start the URL that opens the configuration environment. 2. Choose OCI Mapping. 3. Choose an OCI field and, from the drop down box, select the corresponding SRM-MDM field you want to map. See also: Configuring the Search in the Web Dynpro UI [Page 25] Purpose Setting Up Contract Replication In this section, you make the following settings that are required for the import of contracts from client systems: Setting Up the Key Mapping for Contract Item Categories [Page 30] Implementing BAdI to Enrich Contract Data [Page 31] Configuring Role for Data Import via Import Server [Page 32] Setting Up the Key Mapping for Contract Item Categories Use In this procedure you configure the Key Mapping for the pre-delivered content of the Contract Item Categories table. By default, this table contains the following entries: Normal Product Category If you create your own additional client system(s), you need to maintain the key mapping for the contract item categories. SAP delivers editable key mappings for the mysap SRM and mysap ERP client systems, for example: SRM-MDM Catalog 1.0: Configuration Guide 30