Catalog Content Management - Configuration Guide 2

Catalog Content Management: Configuration Guide

Release 500

ADDON.SRM_CMCONGUIDE

Version 1.3

10.01.2005

Copyright © Copyright 2004 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, and Informix are trademarks or registered trademarks of IBM Corporation 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.

Catalog Content Management: Configuration Guide

2

10.01.2005

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

Description

Example text

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.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

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.

Example text

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.

EXAMPLE TEXT

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

Catalog Content Management: Configuration Guide

3

10.01.2005

Catalog Content Management: Configuration Guide ................................................................ 5 Documentation Landscape for SAP Solutions and Business Scenarios ............................... 7 SAP Notes.............................................................................................................................. 9 System Connections ............................................................................................................ 10 SAP Exchange Infrastructure ........................................................................................... 10 Configuring the System Landscape Directory .............................................................. 10 Defining Technical Connections ................................................................................... 14 Configuring Communication and Security .................................................................... 14 Defining Business Systems in the Integration Builder.................................................. 15 Importing Business Scenarios ...................................................................................... 16 Activating Internet Communication Framework Services ................................................ 17 Setting Parameters for Internet Communication Manager............................................... 18 Creating a URL for SAP Catalog Authoring Tool ............................................................. 18 Using SAP Catalog Content Management with SAP Enterprise Buyer ........................... 19 Mapping Catalog Characteristics to OCI Fields ............................................................... 19 Process Customizing ........................................................................................................... 21 Configuring SAP Catalog Authoring Tool......................................................................... 21 Configuring SAP Catalog Search Engine......................................................................... 23

Catalog Content Management: Configuration Guide

4

10.01.2005

Catalog Content Management: Configuration Guide This business scenario configuration guide applies to the Catalog Content Management business scenario with the corresponding releases of its SAP application components.

Business Scenario and Application Components Business Scenario

Application Component with Minimum Release

Catalog Content Management

SAP Exchange Infrastructure 3.0 SAP SRM Server 5.0 SAP Catalog Content Management 1.0 BugsEye Catalog 4.0.0.25 (for upgrade customers only) SAP Integrated Catalog 3.0 (optional, for upgrade customers only) Requisite eMerge 4.0.0.25 (optional, only for upgrade customers)

Catalog Content Management: Configuration Guide

5

10.01.2005

Catalog Manager

File System

Content Manager in Enterprise Buyer SAP Enterprise Buyer

Catalog Manager

SAP Catalog Authoring Tool

SAP XI

Schema

Convert to SAP XML

Load schema

Catalog files in various formats

Convert to SAP XML

Load external data

Convert to SAP XML

Load internal data

Catalog data

Content Approver

End User SAP Catalog Search Engine

Perform technical quality check Filter catalog data Save products in CAT Map products to schema Enrich product data

Check catalog values Approve product data Check product catalog Define views Publish catalog Route Search for products

Catalog Content Management Component View

Contents The business scenario configuration guide contains all steps required to implement the Catalog Content Management business scenario. The guide specifies the sequence of the configuration activities, and their dependencies. It includes information about the following topics: •

System connections

Catalog Content Management: Configuration Guide

6

10.01.2005 •

Business Customizing

For more information about the Catalog Content Management business scenario, see SAP Service Marketplace at service.sap.com/ibc → …for mySAP SRM.

Target group •

Technical consultants

•

Application consultants

•

Project team members during the implementation of an SAP solution

•

SAP customer IT department

The System Connections section is aimed at technical consultants in particular. The 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 Catalog (CA-CAT) 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

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

Master Guide, Installation and Upgrade Guides

instguides ibc

Business-Scenario Configuration Guide

ibc

Catalog Content Management: Configuration Guide

7

10.01.2005

Implementation Guide (IMG)

Note: This is in the SAP System, not in SAP Service Marketplace

Business Scenario Description

ibc

SAP Library

helpportal with all releases of a SAP component Note: Available in the SAP System under Help → SAP Library

The following information supplements the individual documents: Current supplementary information Information

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

SAP notes

notes to the note search instguides listed by installation and upgrade guide

Technical infrastructure (for example hardware sizing, platforms, network security)

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.

Catalog Content Management: Configuration Guide

8

10.01.2005

SAP Notes Definition This section lists all SAP Notes that are relevant to this Business Scenario Configuration Guide.

Ensure that you read the information contained in the Release Information Note (RIN) for the current support package, as listed in the table below.

SAP Notes Note Number

Title

Referenced in Section

705060

CCM 100 Installation with SAINT

SAP Exchange Infrastructure

517484

Inactive Services in the Internet Communication Framework

Activating Internet Communication Framework Services

783635

System Landscape Options for SAP Catalog Content Management

SAP Exchange Infrastructure,

723129

Support Package 00 for SRM Release 4.0 (RIN)

750433

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

759473

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

769901

SRM 4.0 SP-Stack 10/2004 (SAPKIBKS03): Release and Informat. (RIN)

790376

SRM 4.0 Support Release 01

712105

Support Package 00 for CCM 1.0

750683

Support Package 01 for CCM 1.0

764327

Support Package 02 for CCM 1.0

771462

Support Package 03 for CCM 1.0

783437

Support Package 04 for CCM 1.0

Catalog Content Management: Configuration Guide

Configuring the System Landscape Directory

9

10.01.2005

System Connections Purpose This section contains information about connecting the systems in a SAP system landscape. This involves, for example: •

Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP)

•

Determining the systems, servers, clients, distribution models and so on, 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

Procedure Perform the steps in these guidelines in the sequence in which they appear.

SAP Exchange Infrastructure Purpose In this section, you make settings in SAP Exchange Infrastructure (SAP XI) that are required for the Catalog Content Management scenario. These settings enable you to upload data using SAP XI and enable SRM Server, SAP Catalog Authoring Tool, and SAP Catalog Search Engine to communicate with each other using the Integration Server.

Prerequisites •

You have installed the Integration Server. For more information, see SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver → Release 04 → Installation.

•

You have installed the SAP components that are relevant for the Catalog Content Management business scenario. For more information, see SAP Notes 705060 and 783635.

•

You have imported SAP Exchange Infrastructure content. For more information, see SAP Service Marketplace at service.sap.com/ibc-srm → Master Guide for mySAP SRM (Using SAP Enterprise Buyer 5.0) → Additional Information (Unit 6).

Configuring the System Landscape Directory Use To use SAP Exchange Infrastructure as part of the Catalog Content Management 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 5.0 and SAP Catalog Authoring Tool)

•

The systems that receive messages from SAP Exchange Infrastructure (SAP Catalog Authoring Tool and SAP Catalog Search Engine)

Catalog Content Management: Configuration Guide

10

10.01.2005 In this section, you define the system landscape in the SLD. The graphics below show the possible system landscape options for the Catalog Content Management business scenario. For more information about the advantages and disadvantages of each system landscape option, see SAP Note 783635. The graphics also show 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. Option 1: You use one installation for both SAP Catalog Authoring Tool and SAP Catalog Search Engine.

Web Browser & Client File System Plain HTTP(S) (includes OCI communication)

TREX (2) RFC

CCM Integration Engine

SRM Server Integration Engine

Plain HTTP(S)

XI 3.0 protocol (1)

(1), (3)

(3)

Plain HTTP adaptor

XI 3.0 Integration Server

Numbered connections and the corresponding processes: (1) Uploading catalog content or schemas in XML format to SAP Catalog Authoring Tool. You use an RFC destination in SAP Catalog Content Management to configure the URL of the Integration Server’s plain HTTP adaptor. You use the business scenario CatalogUpload in the Integration Repository. (2) Searching in SAP Catalog Search Engine. (3) Transferring product and contract data from SRM Server to SAP Catalog Authoring Tool. You use the business scenario MasterDataInclusionInCatalog in the Integration Repository.

System Landscape: Option 1

Catalog Content Management: Configuration Guide

11

10.01.2005

SAP Catalog Content Management (SAP CCM) is an add-on. You therefore have the option of using the system landscape shown for option 1, but installing the add-on on the same instance as the component SRM Server. You then have the additional option of using SAP CCM in the same client as SRM Server: •

If you install SAP CCM on the same instance as SRM Server, you do not need to configure a separate technical system for SAP CCM. This does not affect the rest of the configuration process.

•

If you install SAP CCM on the same instance as SRM Server and you use SAP CCM within the same client as Enterprise Buyer, you do not need to configure a separate business system for SAP CCM. This does not affect the rest of the configuration process.

Option 2: You install SAP Catalog Authoring Tool and SAP Catalog Search Engine on two separate systems, or in different clients within the same technical system.

Web Browser & Client File System Plain HTTP(S) (includes OCI communication) RFC

CCM used as Catalog Authoring Tool Integration Engine

SRM Server

CCM used as Catalog Search Engine

Integration Engine

Integration Engine

TREX (2)

XI 3.0 Protocol

Plain HTTP(S) (1)

(1), (3)

(4)

(3)

(4)

Plain HTTP adaptor

XI 3.0 Integration Server Numbered connections and the corresponding processes: (1) Uploading catalog content or schemas in XML format to SAP Catalog Authoring Tool. You use an RFC destination in SAP Catalog Content Management to configure the URL of the Integration Server’s plain HTTP adaptor. You use the business scenario CatalogUpload in the Integration Repository. (2) Searching in SAP Catalog Search Engine. (3) Transferring product and contract data from SRM Server to SAP Catalog Authoring Tool. You use the business scenario MasterDataInclusionInCatalog in the Integration Repository. (4) Publishing procurement catalogs in SAP Catalog Authoring Tool to make them available in SAP Catalog Search Engine. You use the business scenario CatalogPublication in the Integration Repository.

System Landscape: Option 2

Catalog Content Management: Configuration Guide

12

10.01.2005

SAP Catalog Content Management is an add-on. You therefore have the option of using the system landscape shown in option 2, but installing one of the two components (SAP Catalog Authoring Tool or SAP Catalog Search Engine) on the same instance as the component SRM Server. You then have the additional option of using that component within the same client as Enterprise Buyer. •

If you install SAP Catalog Authoring Tool or SAP Catalog Search Engine on the same technical instance as SRM Server, you do not need to configure a separate technical system. This does not affect the rest of the configuration process.

•

If you install SAP Catalog Authoring Tool or SAP Catalog Search Engine on the same instance as SRM Server and use it within the same client as Enterprise Buyer, you do not need to configure a separate business system for that component. This does not affect the rest of the configuration process.

Procedure Configure the technical and business system landscape for the following installed components: •

SRM Server 5.0 (type: SAP business system)

•

Integration Server (type: SAP business system)

•

SAP Catalog Content Management add-on (type: SAP business system) for each installation on a separate Web Application Server, as shown in the graphics above.

For information about configuring the technical and business system landscape, see the documentation in the following table:

Subject

Title of Documentation

Path in SAP Library (help.sap.com)

Configuring the technical system landscape

Manually Registering SAP Web AS ABAP Systems

SAP NetWeaver → Release 04’ → Application Platform (SAP Web Application Server) → Java Technology in SAP Web Application Server → Administration Manual → Server Administration → SAP System Landscape Directory → Configuration for the SAP Exchange Infrastructure → Manually Registering SAP Web AS ABAP Systems

Configuring the business system landscape

Configuring an SAP Business System

Use the path above, and then choose Configuring an SAP Business System

Result You have now defined business systems for each of the above products. In the remainder of the documentation on configuring SAP Exchange Infrastructure, we refer to these business systems as follows:

Catalog Content Management: Configuration Guide

13

10.01.2005 •

Represents the SAP business system for SAP SRM Server 5.0

•

Represents the SAP business system for the integration server If you are using system landscape option 1 (see above):

•

Represents the SAP business system on which you installed SAP Catalog Authoring Tool and SAP Catalog Search Engine If you are using system landscape option 2 (see above):

•

Represents the SAP business system on which you installed the SAP Catalog Content Management add-on and that serves the role of SAP Catalog Authoring Tool

•

Represents the SAP business system on which you installed the SAP Catalog Content Management add-on and that serves the role of SAP Catalog Search Engine

Ensure that you name the business systems consistently. This is especially important if you are configuring multiple SRM scenarios.

Defining Technical Connections Use In this section, you establish a technical connection between the business systems that you are using for SAP Catalog Content Management and the Integration Server.

Prerequisites You have carried out the steps described in Unit 6 (Connecting Business Systems with an Integration Engine to the Central Integration Server) of the configuration guide for SAP Exchange Infrastructure. See SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver → Release 04 → Installation → Configuration Guide – SAP XI 3.0.

Configuring Communication and Security Use In this section, you configure the different protocols and components involved in the communication between SAP Catalog Content Management and the Integration Server.

Procedure ...

To upload supplier product data or catalog schemas in XML format for use in procurement catalogs, you must set up an HTTP connection to the Integration Server in your

Catalog Content Management: Configuration Guide

14

10.01.2005 system or client. To do this, you must create an RFC destination for the HTTP connection to the HTTP adapter of the Integration Server: 1. Define an HTTP connection to the HTTP adaptor of the Integration Server. a. Choose transaction SM59. b. Create an HTTP connection by copying the entry for the Integration Server (by choosing Destination → Copy). c. Enter a name for your new entry. d. On the Technical Settings tab page, replace the path prefix with /sap/xi/adapter_plain. e. On the Logon/Security tab page, re-enter your password. You must do this because the system does not copy your password when you copy the entry for the Integration Server. f. Save your entries. 2. Insert name of the new RFC destination that you created in part 1. (see above) as the RFC destination for uploading catalogs into SAP Catalog Authoring Tool: In Customizing for SAP Catalog Content Management, choose SAP Catalog Authoring Tool → Specify Settings for Uploading Catalogs.

If you are using SAP Catalog Content Management with mySAP Supplier Relationship Management and you want to use secure system connections, you must ensure that the SAP Catalog Content Management systems only accept logon tickets issued from a trusted server. For more information, see SAP Help Portal at help.sap.com → SAP NetWeaver → Security → User Authentication and Single Sign On → Authentication on the SAP Web Application Server ABAP → Using Logon Tickets → Configuring the System for Accepting Logon Tickets. For more information, see: •

SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver → Release 04 → Installation → Configuration Guide – SAP XI 3.0

•

SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver '04 Component Security Guides → SAP Exchange Infrastructure Security Guide

Defining Business Systems in the Integration Builder Use In this section, you define the technical communication parameters between: •

The Integration Server and the SAP Catalog Content Management business system (if you used option 1 in the section Configuring the System Landscape Directory)

•

The Integration Server and the business systems for SAP Catalog Authoring Tool and SAP Catalog Search Engine (if you used option 2 in the section Configuring the System Landscape Directory)

Catalog Content Management: Configuration Guide

15

10.01.2005

Prerequisites In the System Landscape Directory, you have defined the business systems that you want to use (see section Configuring the System Landscape Directory).

Procedure ...

Define the business systems that you are using in the Integration Builder as described in the SAP Exchange Infrastructure documentation: SAP Help Portal at help.sap.com → SAP NetWeaver Release ’04 → Process Integration → SAP Exchange Infrastructure → Design and Configuration Time → Configuration → Defining Collaboration Profiles → Service → Business System (Service) → Business System Assistant.

Note the following when you define business systems in the Integration Builder for SAP Catalog Content Management: {

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

{

In the Select Business System step, select the indicator Create Communication Channels Automatically.

{

Once the Integration Builder has created the communication channels, you must do the following for the generated receiver channel with the adapter type XI:

ƒ

In the Service Number field, enter the HTTP port for the Integration Engine of the business system.

ƒ

Set the authentication type to Use Logon Data for SAP System. You must then enter a user name, user password, logon language, and client.

The Integration Builder generates several communication channels, but only the generated receiver channel with the adapter type XI is relevant for SAP Catalog Content Management. You can delete the other receiver channels, provided you do not need them for other scenarios.

Importing Business Scenarios Use In this section, you can import business scenarios from the Integration Repository and generate them. If you do this, you do not need to generate receiver and interface determinations manually.

You can use the following business scenario templates for SAP Catalog Content Management:

CatalogUpload: Configures supplier product data and catalog schema upload. Note: The component view shows two swim lanes for technical reasons – the business system corresponding to the Catalog Authoring Tool must be assigned to both lanes.

Catalog Content Management: Configuration Guide

16

10.01.2005 CatalogPublication: Configures the publication of catalogs from SAP Catalog Authoring Tool to SAP Catalog Search Engine. You only need to import this business scenario if you used option 2 in the section Configuring the System Landscape Directory.

MasterDataInclusionInCatalog: Configures the transfer of SRM Server product data and contract data to SAP Catalog Authoring Tool.

Prerequisites You have configured the System Landscape Directory (SLD) as described in the section Configuring the System Landscape Directory.

Procedure ...

1. Start the SAP Integration Builder. 2. Choose Tools → Transfer Business Scenario from Integration Repository. 3. On the Objects tab page, choose one of the predefined business scenarios for SAP Catalog Content Management.

All the predefined business scenarios for SAP Catalog Content Management belong to the software component SAP CATALOG CONT. MGMT with the namespace http://sap.com/xi/CCM/CAT. The business scenario configurator opens automatically. 4. Follow the configuration steps in the left-hand frame of the business scenario configurator ensuring that you: {

Enter the generated receiver channel with the adapter type XI (see Defining Business Systems in the Integration Builder) for each connection

{

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

Once you have completed the steps in the business scenario configurator, the system displays a results list. 5. If the results list does not contain any errors, activate the business scenario.

For more detailed information about defining and configuring scenarios, see the SAP Help Portal at help.sap.com → SAP NetWeaver → Release ’04 → Process Integration → SAP Exchange Infrastructure → Design and Configuration Time → Configuration → Defining Scenarios → Business Scenario Configurator.

Activating Internet Communication Framework Services Use You use this procedure to activate HTTP services for SAP Catalog Content Management.

Catalog Content Management: Configuration Guide

17

10.01.2005

Procedure 1. In transaction SICF, activate the nodes listed in the following sections of SAP Note 517484: {

Using Business Server Pages (BSP)

{

Using the BSP logon procedure

2. In the same transaction (SICF), activate all the nodes below ccm: a. Choose default_host → sap → bc → bsp → ccm. b. To activate a node, select the node and choose Service/Virtual Host → Activate.

Setting Parameters for Internet Communication Manager Use You use this procedure to set parameters for Interface Communication Manager (ICM) in transaction SMICM. For detailed information about setting the parameters, see SAP Help Portal at help.sap.com → SAP NetWeaver → Release ‘04 → Application Platform (SAP Web Application Server) → Architecture of the Web AS → Administration of the Internet Communication Manager (ICM).

Ensure that you set the values of the parameter icm/server_port_ correctly for the protocol (HTTP and/or HTTPS). We recommend that you set the value of the network timeout TIMEOUT to 900 seconds.

Creating a URL for SAP Catalog Authoring Tool Use You can use this procedure to define a URL for SAP Catalog Authoring Tool. You need to do this only if you are using SAP Catalog Content Management as a standalone solution.

Procedure ...

1. Start transaction SE80. 2. Display the BSP application /ccm/cat. 3. Choose Pages with Flow Logic. 4. Choose CAT_HOME.htm. 5. On the Properties tab page, copy the entry in the URL field and paste it into a wordprocessing application, for example. 6. In the word-processing application, add the following parameters to the end of the URL: {

sap-client, for example ?sap-client=100

{

sap-sessioncmd, for example &sap-sessioncmd=open

{

sap-language, for example &sap-language=en

Catalog Content Management: Configuration Guide

18

10.01.2005

If you do not specify a language as part of the URL, SAP Catalog Authoring Tool opens in the default language of your browser. The language entered in the user profile does not affect the language in which SAP Catalog Authoring Tool opens.

Result You have created a URL for SAP Catalog Authoring Tool. You can add this URL to your portal or to the favorites of users that have the role(s) required to use SAP Catalog Authoring Tool. (For more information about roles, see Configuring SAP Catalog Authoring Tool in this configuration guide.)

Using SAP Catalog Content Management with SAP Enterprise Buyer Use To use SAP Catalog Content Management with SAP Enterprise Buyer, you must make certain settings in the Enterprise Buyer system. For more information about these settings, see SAP Service Marketplace at service.sap.com/ibc-srm → Self-Service Procurement: Configuration Guide → Configuring SAP Catalog Content Management. If you want to use SAP Catalog Content Management to process SRM contract data, you must define SAP Catalog Content Management as a backend system in the SRM Server system. You do this in Customizing for Supplier Relationship Management, by choosing SRM Server → Technical Basic Settings → Define Backend Systems.

Ensure that you select Catalog in the Sys. type field, when you define SAP Catalog Content Management as a backend system.

Mapping Catalog Characteristics to OCI Fields Use In the standard delivered version of SAP Catalog Content Management, the standard characteristics are already mapped to fields of the Open Catalog Interface (OCI). You can use this procedure to change these standard settings for each catalog individually, and to map non-standard characteristics to OCI fields. The following table lists the predefined characteristics in SAP Catalog Content Management and their corresponding OCI fields: SAP Catalog Content Management Characteristic

OCI Field

/CCM/AMOUNT

NEW_ITEM-PRICE

/CCM/CURRENCY_CODE

NEW_ITEM-CURRENCY

/CCM/CONTRACT_ID

NEW_ITEM-CONTRACT

/CCM/CONTRACT_ITEM_ID

NEW_ITEM-CONTRACT_ITEM

/CCM/IS_SERVICE

NEW_ITEM-SERVICE

/CCM/LEAD_TIME

NEW_ITEM-LEADTIME

Catalog Content Management: Configuration Guide

19

10.01.2005

/CCM/LONG_DESCRIPTION

NEW_ITEM-LONGTEXT_N:132

/CCM/MNFCTR_ID

NEW_ITEM-MANUFACTCODE

/CCM/MNFCTR_PART_NO

NEW_ITEM-MANUFACTMAT

/CCM/ORDER_UNIT

NEW_ITEM-UNIT

/CCM/PRODUCT_GROUP

NEW_ITEM-MATGROUP

/CCM/PRODUCT_ID

NEW_ITEM-MATNR

/CCM/SUPPLIER_ID

NEW_ITEM-VENDOR

/CCM/SUPPLIER_PART_NO

NEW_ITEM-VENDORMAT

For more information about the OCI and OCI field names, see sap.com/partners/icc/scenarios/srm/ → B2B-OCI → Open Catalog Interface.

Procedure ...

1. In SAP Catalog Content Management, open the catalog that you want to edit. 2. On the Schema tab page, select Edit Characteristics. 3. Choose a characteristic that you want to transfer using the OCI. The system displays the details relating to the characteristic that you chose. If the characteristic is already mapped to an OCI field, the field is displayed in the OCI Field field. 4. Enter a new value in the OCI Field field or make changes to the existing entry.

You must enter the OCI field name without the square brackets and anything contained within them.

You want to map the catalog characteristic /CCM/ORDER_UNIT, which contains the unit of measurement to be used in orders. The OCI field for unit of measurement is NEW_ITEM-UNIT[n]. N represents the line number. You must enter NEW_ITEM-UNIT in the OCI Field field. SAP Catalog Content Management adds the information represented by [n] automatically.

The OCI field for long texts is an exception. To map to the long text field, you must enter NEW_ITEM-LONGTEXT_n:132. The ending _n:132 tells SAP Catalog Content Management that it must handle this field differently. Do not include the brackets when you enter this field in the OCI Field field in SAP Catalog Content Management. SAP Catalog Content Management does not check whether you have used the same OCI field for more than one characteristic. This is because, in certain circumstances, it might make sense to map different characteristics in different catalog categories to the same OCI field. If more than one characteristic is mapped to the same OCI field and those characteristics contain values, the value that is transferred to the OCI field last overwrites any values that were previously transferred.

In the standard delivered version of SAP Catalog Content Management, the characteristic /CCM/SUPPLIER_ID is mapped to the OCI field NEW_ITEMVENDOR. On schema level, you create the additional characteristic Vendor, map it to the same OCI field (NEW_ITEM_VENDOR), and publish the catalog.

Catalog Content Management: Configuration Guide

20

10.01.2005 You transfer an item for which both characteristics are filled (the characteristic /CCM/SUPPLIER_ID with the value 1000, and the Vendor characteristic with the value 1050) to the shopping cart. The characteristic value that is transferred to the OCI field last, overwrites the characteristic value that was transferred first. The OCI field NEW_ITEM_VENDOR can therefore have the value 1000 or 1050, depending on which characteristic value was transferred last.

Process Customizing Purpose This section contains information about the process Customizing settings in the SAP Catalog Content Management system.

Process Flow Perform the steps in the sequence in which they appear.

Configuring SAP Catalog Authoring Tool Use SAP Catalog Content Management consists of the components SAP Catalog Authoring Tool and SAP Catalog Search Engine. This procedure describes the Customizing settings you must make in the business system that has the role of SAP Catalog Authoring Tool.

Prerequisites If you want to upload supplier catalogs that are not in CSV format, you have: •

Created an RFC destination to enable SAP Catalog Authoring Tool to communicate with the plain HTTP adaptor of the Integration Server

•

Entered this RFC destination in the IMG activity Specify Settings for Uploading Catalogs

For more information, see the Configuring Communication and Security section of this configuration guide.

Procedure ...

1. In Customizing for SAP NetWeaver: {

Define a logical system for the client that you are using for SAP Catalog Authoring Tool by choosing SAP Web Application Server → Application Link Enabling (ALE) → Basic Settings → Logical Systems → Define Logical System

{

Assign the client to the logical system by choosing SAP Web Application Server → Application Link Enabling (ALE) → Basic Settings → Logical Systems → Assign Client to Logical System

Catalog Content Management: Configuration Guide

21

10.01.2005

If you are using one client for both SAP Catalog Authoring Tool and SAP Catalog Search Engine, you need to carry out this step once only (for SAP Catalog Content Management as a whole). 2. In Customizing for SAP Catalog Content Management, make the following settings, by choosing Cross-Application Settings → Assign Roles: If you want to upload supplier catalogs in CSV format only: {

Generate authorization profiles for the roles of Catalog Manager (/CCM/CATALOG_MANAGER) and Content Approver (/CCM/CATALOG_APPROVER)

{

Assign users to these roles

If you want to upload supplier catalogs that are not in CSV format: {

Generate authorization profiles for the roles of Catalog Manager (/CCM/CATALOG_MANAGER), Content Approver (/CCM/CATALOG_APPROVER), and SAP Exchange Infrastructure server user (SAP_XI_APPL_SERV_USER)

{

Assign users to these roles, ensuring that you assign the user that you entered in the logon data for the generated XI receiver channel (see Defining Business Systems in the Integration Builder) to the roles /CCM/CATALOG_MANAGER and SAP_XI_APPL_SERV_USER

3. In Customizing for SAP Catalog Content Management, choose SAP Catalog Authoring Tool → Specify Settings for Publishing Catalogs. In this IMG activity you specify: {

Whether catalogs are published locally

{

How many objects (catalog items or categories) are transferred in each package during the publishing process

4. If you are using SAP Catalog Content Management as a standalone solution, define number ranges for external business partners in Customizing, by choosing CrossApplication Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges and Define Groupings and Assign Number Ranges. After Configuration •

When SAP Catalog Authoring Tool is used for the first time, you must open the Edit Catalogs application once, before you create any catalogs. Choosing Edit Catalogs triggers the creation of the master catalog. If you do not do this, SAP Catalog Authoring Tool outputs an error message when you try to create a catalog.

•

As of SAP Catalog Content Management 1.0, support package 01, you must use transaction SA38 to run report /CCM/INITIALIZE_CME before you use SAP Catalog Authoring Tool for the first time. The report checks the Customizing settings you have made and, providing those settings are correct, unpacks the predefined characteristics. If you do not run this report, SAP Catalog Authoring Tool outputs an error message when you try to open an application.

If you run SAP Catalog Authoring Tool and SAP Catalog Search Engine in separate clients, you must also run this report in the SAP Catalog Search Engine client (see Configuring Catalog Search Engine).

Catalog Content Management: Configuration Guide

22

10.01.2005

Configuring SAP Catalog Search Engine Use SAP Catalog Content Management consists of the components SAP Catalog Authoring Tool and SAP Catalog Search Engine. This procedure describes the Customizing settings you must make in the business system that has that role of SAP Catalog Search Engine.

Prerequisites You have installed and configured Search and Classification (TREX). For more information about installing and configuring TREX, see the installation guide for TREX 6.1: SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver → Release 04 → Installation → Installation Guide – Search and Classification (TREX).

Note the following when you configure TREX: {

SAP Catalog Content Management uses RFC connections to communicate with TREX. Perform the steps to set up an RFC destination only (see Checklists for the Installation → Installation with RFC Connection).

{

Automatic language recognition is not required. You can adopt the default settings for document languages during the installation of TREX.

{

No Python extensions are required.

{

A search server relation is not required.

{

SAP Catalog Content Management uses the TREX ABAP client only.

{

We recommend that you configure several RFC server instances for TREX. For more information, see the section Configuring the Number of Registered RFC Servers in the installation guide for TREX 6.1.

Procedure ...

1. In Customizing for SAP NetWeaver: {

Define a logical system for the client that you are using for SAP Catalog Search Engine by choosing SAP Web Application Server → Application Link Enabling (ALE) → Basic Settings → Logical Systems → Define Logical System.

{

Assign the client to the logical system by choosing SAP Web Application Server → Application Link Enabling (ALE) → Basic Settings → Logical Systems → Assign Client to Logical System.

If you are using one client for both SAP Catalog Authoring Tool and SAP Catalog Search Engine, you need to carry out this step once only (for SAP Catalog Content Management as a whole). 2. If you are using SAP Catalog Content as a standalone solution, generate authorization profiles for the role of Catalog User (/CCM/CATALOG_SEARCH) and assign users to the role. You make these settings in Customizing for SAP Catalog Content Management, by choosing Cross-Application Settings → Assign Roles. 3. In the SAP Catalog Content Management system, create RFC destinations with the activation type Registration for TREX using transaction SM59. The number of RFC destinations that you need to create depends on the number of RFC destinations that you want to use in step 4.

Catalog Content Management: Configuration Guide

23

10.01.2005 For more information about creating RFC destinations for TREX, see the section Creating an RFC Destination (Registration) in the installation guide for TREX 6.1. 4. In Customizing for SAP Catalog Content Management, create the connection between SAP Catalog Search Engine and TREX, by choosing SAP Catalog Search Engine → Specify RFC Destinations for TREX and entering the RFC destination(s) that you defined for TREX in step 3.

If you simultaneously transfer large volumes of data to TREX indexes for different languages, creating and assigning more than one RFC destination for TREX may help improve performance. You must enter a different language for each RFC destination. After Configuration As of SAP Catalog Content Management 1.0, support package 01, you must use transaction SA38 to run report /CCM/INITIALIZE_CME before you use SAP Catalog Search Engine for the first time. The report checks the Customizing settings you have made and, providing those settings are correct, unpacks the predefined characteristics. If you do not run this report, SAP Catalog Search Engine outputs an error message when you try to open the application.

If you are using one client for both SAP Catalog Authoring Tool and SAP Catalog Search Engine, you need to run the report once only (for SAP Catalog Content Management as a whole).

Catalog Content Management: Configuration Guide

24