Config Guide ECO ERP 50

Configuration Guide

SAP E-Commerce for mySAP ERP: Business Scenario Configuration Guide

Release 5.0

Configuration Guide

Copyright © Copyright 2005 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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 and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com 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 trademarks of their respective companies.

10.11.2005

2

Configuration Guide

Icons Icon

Meaning Caution Example Note Recommendation Syntax Link to SAP Help Portal

Typographic Conventions Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

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. Pointed brackets indicate that you replace these words and characters with appropriate entries.

10.11.2005

3

Configuration Guide

Contents 1

PURPOSE...........................................................................................................................................................7

2

CONFIGURATION...........................................................................................................................................7 2.1 ERP E-COMMERCE SYSTEM PREREQUISITES ..........................................................................................7 2.2 CONFIGURING THE WEB APPLICATION ......................................................................................................8 2.2.1 Extended Configuration Management (XCM).................................................................................8 2.2.2 Bookmark Support for B2C E-Commerce .....................................................................................16 2.2.3 XCM Settings for Transaction Maintenance .................................................................................17 2.2.4 Web Application Specific Parameters............................................................................................18 2.2.5 Administration of Language and Country Settings.......................................................................20 2.2.6 Tax Determination using the IPC in ERP E-Commerce..............................................................21 2.2.7 Material Number Format Conversion .............................................................................................22 2.2.8 Delivery Priority Field Configuration ...............................................................................................22 2.3 ADMINISTRATING THE WEB APPLICATION ................................................................................................23 2.3.1 Administration of the Web Application ...........................................................................................23 2.3.2 Catalog Cache Statistics..................................................................................................................24 2.3.3 System Cache Statistics ..................................................................................................................24 2.3.4 Java Connector Statistics ................................................................................................................25 2.3.5 Web Application Specific Parameters............................................................................................26 2.4 LOGGING WEB APPLICATION ...................................................................................................................26 2.5 CONNECTIVITY ..........................................................................................................................................27 2.6 CONFIGURING USER MANAGEMENT IN ERP E-COMMERCE ...................................................................31 2.6.1 ERP E-Commerce SU01 Logon .....................................................................................................32 2.6.2 Configuration Settings for User Management in ERP E-Commerce.........................................35 2.6.3 Configuring the Authorization Concept in ERP E-Commerce ....................................................43 2.7 SHOP MANAGEMENT ................................................................................................................................50 2.7.1 Shop Management in ERP E-Commerce......................................................................................50 2.7.2 Setting Up Free Goods.....................................................................................................................52 2.7.3 Using Structured Products and Bills of Material ...........................................................................53 2.8 SETTING UP ORDER CONFIRMATION VIA E-MAIL ....................................................................................54 2.8.1 Creating Output Condition Records ...............................................................................................54 2.8.2 Maintaining Document Distribution Settings .................................................................................55 2.9 SETTING UP SHIPPING STATUS TRACKING .............................................................................................56 2.9.1 Access Delivery Tracking Status ....................................................................................................56 2.9.2 Preparing Tables ...............................................................................................................................57 2.9.3 Creating a Vendor .............................................................................................................................58 2.9.4 Creating an Express Delivery Company........................................................................................58 2.9.5 Including Express Delivery Company Requirements ..................................................................61

3

BUSINESS PROCESSES ................................................................................................................................64 3.1 AUCTION PAYMENT AND DELIVERY PROCESSING IN ERP E-COMMERCE ..............................................64 3.1.1 Configuration of Web Auctions: Selling via eBay® in ERP.........................................................64 3.1.2 Delivery Processing ..........................................................................................................................65 3.2 BILLING IN ERP ........................................................................................................................................67 3.3 BROWSING FOR AND SELECTING PRODUCTS IN ERP ............................................................................71 3.4 INQUIRY PROCESSING FOR INTERNAL USERS IN ERP E-COMMERCE ....................................................72 3.4.1 External System Scenario: Prerequisites ......................................................................................73 3.5 INQUIRY PROCESSING IN ERP.................................................................................................................74 3.6 INTERACTIVE CONFIGURATION.................................................................................................................76 3.7 MANAGING AUCTIONS FOR SELLING VIA EBAY® IN ERP E-COMMERCE................................................77 3.7.1 Configuration of Web Auctions: Selling via eBay® in ERP.........................................................77 3.7.2 Activities .............................................................................................................................................77 3.8 MANAGING CATALOG CONTENT IN ERP .................................................................................................79 3.8.1 Creating the Directory for Document Publication .........................................................................81

10.11.2005

4

Configuration Guide 3.8.2 Maintaining Properties fort he Default FTP Site ...........................................................................81 3.8.3 Creating and Displaying Multimedia Documents..........................................................................82 3.8.4 XCM Settings for Search Functions in the Product Catalog.......................................................83 3.8.5 Replication of Product Catalog from ERP to TREX .....................................................................84 3.9 QUOTATION PROCESSING IN ERP...........................................................................................................86 3.10 SALES ORDER PROCESSING B2B FOR OCCASIONAL USERS IN ERP E-COMMERCE............................88 3.10.1 Setting Up Order Tracking ..........................................................................................................89 3.10.2 External System Scenario: Prerequisites .................................................................................90 3.10.3 Setting Up the Display of Invoices .............................................................................................90 3.11 SALES ORDER PROCESSING B2B IN ERP E-COMMERCE ......................................................................91 3.11.1 Order Processing .........................................................................................................................92 3.11.2 Defining Type of Availability Check ...........................................................................................93 3.11.3 Setting Up Order Tracking ..........................................................................................................94 3.11.4 External System Scenario: Prerequisites .................................................................................94 3.11.5 Setting Up the Display of Invoices .............................................................................................94 3.11.6 Configuring Grid Product Processing ........................................................................................94 3.12 SALES ORDER PROCESSING B2C IN ERP E-COMMERCE......................................................................96 3.12.1 Order Processing .........................................................................................................................97 3.12.2 Define Type Availability Check...................................................................................................97 3.12.3 Setting Up Order Tracking ..........................................................................................................97 3.12.4 External System Scenario: Prerequisites .................................................................................97 3.13 SALES ORDER PROCESSING FOR INTERNAL USERS IN ERP E-COMMERCE .........................................98 3.13.1 Define Type Availability Check...................................................................................................99 3.13.2 Setting Up Order Tracking ..........................................................................................................99 3.13.3 External System Scenario: Prerequisites .................................................................................99 3.13.4 Setting Up the Display of Invoices.............................................................................................99 3.13.5 Configuring Grid Product Processing ........................................................................................99 3.14 SALES ORDER PROCESSING ONE-STEP BUSINESS IN ERP E-COMMERCE ........................................100 3.14.1 Setting Up Supplier Relationship Management for ERP E-Commerce..............................101 3.15 WEB ANALYSIS IN ERP..........................................................................................................................104 3.16 WEB SITE MONITORING IN ERP ............................................................................................................105

10.11.2005

5

Configuration Guide

Important information regarding this document This document is an extract of SAP Solution Manager configuration information from December 2005. Only business scenarios related to SAP E-Commerce for mySAP ERP are covered in this document. SAP Solution Manager is the main source of configuration information for all SAP solutions. In addition this supplementary document is provided for SAP E-Commerce for mySAP ERP customers as a one time effort. Please note that any updates or corrections to SAP Solution Manager content as of December 2005 will not be included in this document. This document will not be maintained by SAP.

Harmonized naming for SAP E-Commerce To have one common name for SAP's E-Commerce applications we harmonized our naming. The E-Commerce capabilities of mySAP CRM and mySAP ERP now share the common name "SAP ECommerce". SAP E-Commerce can be deployed with SAP CRM, SAP ECC (mySAP ERP) or with SAP R/3 back-end. If the context (back-end) is clear, the following name is used: SAP E-Commerce If the reference to used back-end is important, the following names are used: ƒ SAP E-Commerce for mySAP CRM ƒ SAP E-Commerce for mySAP ERP The term "SAP Internet Sales (R/3 Edition)" is replaced by "SAP E-Commerce for mySAP ERP". It will be used synonymously also in cases where you use the SAP E-Commerce application together with an SAP R/3 back-end. Only if there is an important difference between handling of an ERP or R/3 back-end, the term "SAP E-Commerce for SAP R/3" is used. However the current name for the CRM Key Capability remains as mySAP CRM E-Commerce. The usage of the name "SAP Internet Sales", "SAP Internet Sales in mySAP ERP" and "SAP Internet Sales (R/3 Edition)" will be discontinued. You will still find the former names in certain areas of the documentation as the new naming conventions will only be used when new documents are produced or adapted. This information can also be accessed using the SAP note 817119.

10.11.2005

6

Configuration Guide

SAP E-Commerce for mySAP ERP 5.0: Business Scenario Configuration Guide

1

Purpose

The ERP E-Commerce: Business Scenario Configuration Guide contains all of the configuration steps that are required to set up the following business processes for ERP E-Commerce: ƒ Auction Payment and Delivery Processing in ERP E-Commerce ƒ Billing in ERP ƒ Browsing For and Selecting Products in ERP ƒ Inquiry Processing for Internal Users in ERP E-Commerce ƒ Inquiry Processing in ERP ƒ Interactive Configuration ƒ Managing Auctions for Selling via eBay in ERP E-Commerce ƒ Managing Catalog Content in ERP ƒ Quotation Processing in ERP ƒ Sales Order Processing B2B for Occasional Users in ERP E-Commerce ƒ Sales Order Processing B2B in ERP E-Commerce ƒ Sales Order Processing B2C in ERP E-Commerce ƒ Sales Order Processing for Internal Users in ERP E-Commerce ƒ Sales Order Processing one-Step Business in ERP E-Commerce . ƒ Web Analysis in ERP ƒ Web Site Monitoring in ERP

2 2.1

Configuration ERP E-Commerce System Prerequisites

The following table contains an overview of the technical components needed for ERP E-Commerce. The table displays the minimum and maximum releases for the components, and whether they are mandatory or optional. Technical Component R/3 Server Plug-In for OLTP

Functions of Component (within scenario) All scenarios Data Exchange R/3 4.6c, R/3 4.7, ERP 2004

Minimum Release 4.6c PI 2004.1 SP10

Maximum Release SAP ECC 6.0 Part of SAP ECC 6.0

SAP BW

Business Information Warehouse

CRM Java Applications, CRM Java Components

E-Selling

BW 3.5 BI Content 3.5.2 Add-on 5.0

BW 7.0 BI Content 7.0.2 Add-on 5.0

10.11.2005

Classification Mandatory Mandatory for R/3 4.6c, R/3 4.7, ERP 2004. In SAP ECC 6.0 it is not necessary as it is integrated in the SAP ECC 6.0. Optional Mandatory

7

Configuration Guide Technical Component SAP Shared Java Applications

Functions of Component (within scenario) IPC, Workforce Deployment, E-Selling, Channel Management

Minimum Release 5.0

Maximum Release 5.0

IPC, Workforce Deployment, E-Selling, Channel Management

5.0

5.0

Mandatory if the Java components are modified in the NWDI

Tealeaf

Tealeaf Java API

3.1

4.5

STRUTS

Struts API

1.2

1.2

J2SE, Java Development Kit SAP Web AS Java TREX

Java Virtual machine to run the software Provides the servlet engine Search Engine and Textmining Engine

J2SE 1.42_08

J2SE 1.42_08

Mandatory if the Java components are modified in the NWDI Mandatory if the Java components are modified in the NWDI Mandatory

7.0

7.0

Mandatory

TREX 7.0

TREX 7.0

Optional

7.00

7.0

Optional.

SAP Java Dictionary SAP Shared Java Components SAP Shared Web Components

Classification Mandatory

CRM IPC Mobile

IPC on separate AP box

Relevant only if you are using a SAP R/3 release lower than ERP 2005.

We recommend the following minimal screen resolutions for your Internet browser:

ƒ ƒ

B2B: 1024 * 768 pixel B2C: 800 * 600 pixel

2.2

Configuring the Web Application

2.2.1 Extended Configuration Management (XCM) Use You use the Extended Configuration Management (XCM) Administration tool to configure Web applications, once you have installed the Web components. You use it to make configuration settings needed at runtime. 10.11.2005

8

Configuration Guide The CRM Web applications are used in the following scenarios: ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ

CRM E-Commerce ERP E-Commerce Selling via eBay in CRM and ERP Channel Management Interaction Center Interaction Center WebClient Interaction Center Workforce Management Internet Customer Self-Service SAF

You only have to set up XCM configuration settings for those Web applications that are relevant to the scenarios and processes you are using. The XCM user interface is used for Java-side configuration of the Web application. You have to maintain two setting types in XCM: ƒ

General Settings

Once set, these settings are valid for the whole Web application. These settings are located in the XCM tool under Start → General Settings → Customer. ƒ

Additional Web application configuration settings

Web applications can have multiple configurations with different settings. Depending on the configuration used, the application behaves differently at runtime. Yu can define a default configuration or select the configuration to be used at runtime.

Not all applications support multiple application configurations. Some only support general settings. Some Web applications can run different configurations in different client sessions simultaneously. Each Web application provides one or more predefined (SAP) configurations, which you can find under Start → Application Configurations → SAP. You create a new customer configuration based on these predefined configurations and adjust it to your requirements. You then find your customer configuration under Start → Application Configurations →Customer. Each customer configuration contains: ƒ ƒ ƒ

A configuration name Base configurations (from SAP on which you base your configuration) A number of configuration parameters with associated values which you adjust.

The combination of these two setting types represent the final Web application configuration.

Procedure The following steps explain how to configure a Web application in XCM, assuming you have deployed the application.

10.11.2005

9

Configuration Guide

Starting XCM 1. You access the XCM tool at: http://://admin/xcm/init.do

You can also start XCM in accessibility mode (according to Section 508 Rehabilitation Act) at the following URL: http://://admin/xcm/init.do?sap-accessibility=x 2. Provide a user and password. If you are logging on for the first time use the Administrator user. the password you defined during the installation of NetWeaver

We recommend you create new users with lesser rights than the Administrator fort he administration of Web applications. See the SAP CRM Security Guide section E-Commerce for further details. 3. When the application opens a closed control tree is displayed on the left of the screen. A screen containing help information is displayed to the right. You can use edit (change settings) or display (see settings) mode in XCM. You use the button in the top right hand corner of the screen to change between modes. When you switch to edit mode a DB lock is set meaning that only this user can edit the settings at one time. The lock is released once the user switches back to display mode or after session timeout (default timeout is 30mins).

Printable Help There is a printable help function for the application configuration and components. You access it by selecting Help in the header area of the main XCM Admin window. Within the documentation hyperlinks provide links to more detailed information. The documentation displays the general settings separately.

General Settings You set the general settings and they are valid for the whole Web application. Proceed as follows: 1. Choose the Edit mode and select Start → General Settings → Customer. The system displays the available nodes categorizing the general settings. Depending on the application you will have one or more tree nodes. For information on the possible settings, see the printable help information. 2. Expand a configuration node and select the right hand configuration node to see possible configuration parameters in the right hand window. 3. Select a parameter and enter the settings values that meet your requirements. Each parameter contains a help description for information on what you need to enter. Some parameters have default values set. When you change the values of these default parameters the system will mark them orange. You can revert back to the original default entry by selecting R (revert). 4. Select Save Configuration.

10.11.2005

10

Configuration Guide If your Web application does not support multiple configurations, you are now finished with the General Settings section. You can return to display mode and restart the Web application to activate your changes. If your application does support multiple configurations, see the section below Multiple Application Configurations.

Multiple Application Configurations Once you have set the General Settings you can now configure the various configurations that you need.

Delivered SAP Configuration You need to find out which SAP application configurations are delivered. In more complex applications, for example CRM E-Commerce, there are several pre-configured applications. In simpler applications, for example the User Management application, there are normally fewer, or only one, applications configurations. You display the list in the pre-configured scenarios under Start → Application Configurations → SAP in the control tree. Look through the configurations and choose the one that most suits your requirements.

Create a Customer Application Configuration Once you have selected the configuration that suits your needs go to Edit mode. 1. Enter a configuration Name and choose Create. 2. Configure the application configuration by associating configuration data with the configuration parameters. There is a description for the scenario of each configuration parameter in the last column of the parameter table.

During installation, only those parameters (mandatory) are displayed that are needed to get the application running. Optional parameters can be viewed and edited by selecting Display Advanced Settings.

Configure a Customer Application Configuration Once you have created the application configuration you need to configure it by changing the parameter values. 1. Select Configuration Documentation to see a list of the parameters to be configured. 2. Select a parameter and use the dropdown list box to assign a value. You can display a description of possible values by selecting the ? help button next to the drop down list box. If there is more details description for a parameter an additional ? button is displayed. 3 3. There are two value types: 10.11.2005

11

Configuration Guide ƒ

ƒ

Static Values Values that can be selected from a dropdown list box. These values do not have a button in the Component Configuration column. Values based on Component Configuration You first have to configure a component, for example a connection to your SAP CRM system, before assign the configured value to the parameter. These parameters have a button in the Component Configuration column. For example the jco button for configuring connection parameters to the SAP system

If no value is assigned to these parameters you have to create a new component configuration. For more information see the section Creating a New Component Configuration. If a value is assigned, it is most likely you will not have to change anything during the installation.

Creating a New Component Configuration A component is an independently configurable part of the application (for example the jco component which enables connections between the SAP system and the Web application). A component can have several configurations, for example to different systems and clients. You assign one of the component configurations to the parameter in the application configuration. We recommend you create the component configuration at the same time as you set up the application configuration. 1. Select an empty entry in the dropdown list box for the parameter or choose create component configuration. The system switches to the component creation screen. The correct component, for example jco, is selected automatically and the system display a description of the use of the component. 2. Enter a name for the component configuration (for example Q5C_505 for the Q5C system with client 505) and choose Create. The application switches to the component configuration parameters screen. 3. Select a base configuration from the Base Configuration dropdown list box. A description is displayed using the ? button. 4. Enter values for the component configuration parameter and choose Save Configuration. Test your values in the Configuration Test area.

Testing a Component Configuration Once you have created the component configuration, save it and test it as follows. 1. Select the test from the Select Test dropdown list box for the configuration. You can see a description by selecting the ? button. 2. Choose Run Test. 3. The system displays the test results in a new window. A red traffic light indicates the test failed and you must redo the configuration. A green traffic light indicates the test was successful. 4. Return to the application configuration, by selecting Back to Application Configuration and select the newly created configuration from the dropdown list box and assign it to the scenario parameter.

10.11.2005

12

Configuration Guide

Define a Default Application Configuration You normally carry out this step after assigning values to all configuration parameters. If you have only one application configuration, the system will use it automatically when you start the application. If you have more than one application configuration you must select the Default Configuration checkbox for one of the configurations, so that the system will run this one as default when you start the application.

A green icon in the control tree indicates the default configuration.

Save the Application Configuration Once you have assigned values to all your application configuration parameters you have to save it. 1. 2.

Select Save Configuration. Check the option Active Configuration. If you do not check this field the configuration will be disabled and won’t run when you start the application. If you uncheck this box you determine that the configuration is disabled.

A red icon indicates the configuration is disabled. 3.

The system saves the new application configuration to the SAP Web AS Java 7.0 and it can then be displayed in the customers part of the control tree in XCM.

Activating the Application Configuration Before a new application configuration can become active you have to stop and restart the Web application or, alternatively, restart the SAP Web AS Java 7.0 server. 1. 2. 3.

Start the J2EE Visual Administrator. Connect to the SAP Web AS Java 7.0 server. Choose Server node → open services node → Select deploy service → application and stop and start the Web application.

For more information, see the SAP Web AS Java 7.0 configuration documentation in SAP Solution Manager.

Running the Web Application When you run the Web application the system needs to know which application configuration to use if there is more than one. You can set this up in one of three ways:

10.11.2005

13

Configuration Guide ƒ

ƒ

ƒ

Use the default configuration. Simply start the application and the configuration you set as default will be used. If you have just one configuration this will automatically be the default. For example if you want to call up the default configuration for the b2b Web shop the URL will look as follows: http://:/b2b/b2b/init.do. Specify the application configuration name as a request parameter. In this case you run the application using a different application configuration to the default. You pass the name of the application configuration sing the request parameter configuration.xcm when calling the application. The scenario name is case sensitive. For example if you want to call up the application configuration myB2BCRM the URL will look as follows: http://:/b2b/b2b/init.do?configuration.xm=myB2BCRM Display a start up page containing links to all active configurations and starting the specific application configuration by using the link.

The start page is disabled after installation. You enable it using the following XCM parameter: Start → General Settings → → show.start.jsp.

Uploading and Downloading XCM Settings You can up and download application configurations. In XCM navigate to Start → XCM Settings and you can view the upload and download sections. Each section refers to two objects: ƒ ƒ

Component configuration data Application configuration data

These two objects make up the application configurations of a Web application.

Downloading XCM Configurations This enables you to download XCM configuration form the SAP Web AS Java 7.0 database to XML files. Proceed as follows: 1. Select the download button for the component configuration data file. The system generates a file named config-data.xml containing all component configuration data saved for the Web application. 2. Select the download button for the application configuration data file. The system generates a file named scenario-config.xml containing all application configuration data saved for the Web application.

Uploading XCM Configurations This function enables you to upload XCM configuration data from XML files to the SAP Web AS Java 7.0 server. Proceed as follows: 1. 2. 3.

Select the Edit button. The system displays two file input fields in the upload section. Specify the config-data.xml (component configuration) and scenario-config.xml (application configuration) files, with complete file system paths for both files, and select Upload.

10.11.2005

14

Configuration Guide

For the b2b and b2c Web applications in SAP E-Commerce the XCM administration tool provides a switch to a separate maintenance view for the IPC-specific part of the application (see IPC Switch for XCM Configuration of SAP E-Commerce below). When switching to IPC you can up and download the IPC application and component configurations. The IPC application configuration file is ipcscenarioconfig.xml, the component configuration file is ipcconfig-data.xml.

If you intend to transport XCM when doing a system copy within the CRM 5.0 release, refer to the chapter Data Storage Security in the CRM Security Guide for E-Commerce.In addition to the XCM data you have to also transport encryption keys used in Secure Storage of the SAP Web AS Java 7.0 engine.

Web applications based on CRM 4.0 do not save XCM settings in a database and they do not support the upload and download functionality described in this section. In CRM 4.0 the XCM settings are saved as XML files (config-data.xml for component configuration and scenario-config.xml for application configurations) in a dedicated directory of the J2EE servers file system. You can find the location of the files in XCM Administration under Start → Options. You can upload these configuration files from CRM 4.0 to CRM 5.0 during an upgrade. After migrating XCM settings from an older to a newer Web application version you must check if any of the customer-made XCM settings are obsolete see Indication of Obsolete XCM settings below). The new version may require you to change or give you the option of maintaining additional XCM settings. You add these settings manually, as described in the section Configure a Customer Application Configuration above.

Indication of Obsolete XCM Settings After migrating XCM settings from and older to a newer Web application version, some settings may mo longer be supported in the new version. If these settings were customer-made, meaning they have been changed from their SAP delivered default values, the system will mark them as obsolete by highlighting them in yellow. The following parameters can be specified as obsolete: ƒ ƒ ƒ ƒ ƒ

Application configurations (marked with an exclamation mark on yellow background) Application configuration parameters (highlighted in yellow) Components (marked with an exclamation mark on yellow background) Component configurations (marked with an exclamation mark on yellow background) Component parameters (highlighted in yellow)

IPC Switch for XCM Configuration of SAP E-Commerce The SAP E-Commerce B2B and B2C Web applications each support two application configurations that must be maintained separately: 10.11.2005

15

Configuration Guide ƒ ƒ

The E-Commerce application configuration, which allows the configuration of the overall application The IPC application configuration, which allows additional configuration of the IPC-specific part of the application.

When you start the XCM administration tool for B2B or B2C a dropdown list box is displayed in the upper left corner of the screen. This dropdown list box enables you to switch between the maintenance views for the E-Commerce and IPC application configurations. All features of the XCM Administration tool, that is application configuration maintenance and their upload and download, can be used separately for both the E-Commerce and IPC application configurations.

2.2.2 Bookmark Support for B2C E-Commerce Use You configure bookmark support for B2C CRM E-Commerce to enable customers to add favorites to their Web browser. Adding favorites to the Web browser enables customers to use the favorite links to enter back in to the Web shop process flow where they left it. The bookmark function works even after a session has expired and so is very useful to customers as they do not need to go through the long process of looking for the same product each time they leave and re-enter the Web shop. You can even use bookmarks to enable customers to enter non-standard entry points in the Web shop from outside Web browser, for example entry to the Store Locator from an external browser.

Procedure You enable bookmark support in B2C E-Commerce in the Extended Configuration Management (XCM) application for your B2C Web shop: Log on to XCM at: http///b2c/admin/xcm/init.do: 1.

Choose Start → General Settings → Customer → B2c → b2cconfig.

Set the ReInvokeEnabledparameter to True. This setting enables the bookmark support independently of session timeouts 2.

Choose Start → Components → Customer → shop → .

Enter a shop ID value for the defaultShopID parameter. If you have more than one B2C Web shop and fail to maintain a value here, the entry point for any bookmark will be the shop selection screen. If you need bookmark support in more than one shop you must create an application configuration for each shop to support the bookmark functionality. 3.

Choose Start → General Settings → Customer → ui → .

Enter a language ID value for the language parameter.This parameter sets the application language.

10.11.2005

16

Configuration Guide

Result A B2C Web shop customer can save any step in the application flow as a Web browser bookmark and use this bookmark hyperlink to re-enter the Web shop at this specific step.

2.2.3 XCM Settings for Transaction Maintenance Use You need to enable certain parameters in Extended Configuration Management (XCM) for SAP ECommerce to adapt transaction maintenance to your own needs.

Procedure 1. Log on to Extended Configuration Management (XCM) at http:////admin/xcm/init.do. 2. Navigate to Start → Components → Customer → basket → and adjust the following parameters: Parameter lineItemIncrement

Description This parameter defines the increment of line item numbers. The default setting is 10. So line item numbers will therefore 10, 20, 30, and so on. If you change the value to 100, the line item numbers will be 100, 200, 300, and so on.

usedatabaseBasket

This parameter is only relevant if the base configuration of your component configuration is “javabasket”. Choose the value True to enable the possibility of recovering lost shopping baskets, for example due to session expiry. If you enable this recovery functionality the shopping basket will be written to the SAP Web AS Jave 7.00 database during a Web session instead of just being kept in the main memory. If the session expires and the shopping basket is lost it will automatically be recovered the next time the user logs on to the Web shop. The function works in two ways: • •

Using cookies if the user was not logged on when maintaining the shopping basket. Via User logon ID if the user was logged on the Web shop when maintaining the shopping basket. This parameter is only relevant for a B2C Web shop scenario.

usedatabaseTemplate

10.11.2005

Enabling this functionality may increase the performance hardware requirements. Choose True to enable the use of Order templates in ERP ECommerce. In addition you have to enable the use of order templates in the Shop Management application. If both settings are 17

Configuration Guide Parameter

Description made order templates will be saved to and read from the SAP Web AS Java 7.00 server. The XCM setting is not necessary in CRM E-Commerce as there the order templates are written to the CRM database.

Shopping basket recovery and order template usage in ERP E-Commerce are based on your using the SAP Web AS Java 7.00 server. You have to configure integration between this server and your database according to your application load. Important parameters for integration the SAP Web AS Java 7.00 server with your database can be found using the servers’ visual administration tool. The visual administration tool (visualadmin.bat or visualadmin.sh) can be found in the server directory …/