mysap e-commerce config guide

SAP ECC 6.00 April 2007 English

SAP E-Commerce for mySAP ERP

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Configuration Guide

SAP Best Practices SAP E-Commerce for mySAP ERP: Configuration Guide

SAP AG Page 2 of 62

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

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.


SAP AG Page 3 of 62

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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.


SAP AG Page 4 of 62

Contents 1 Purpose ........................................................................................................................... 7 2 Preparation ..................................................................................................................... 7

2.1 Prerequisites ............................................................................................................ 7 2.1.1 SAP Notes ....................................................................................................... 8

3 Basic Configuration ......................................................................................................... 8 3.1 Product Catalog ....................................................................................................... 8

3.1.1 General Information about the Product Catalog .............................................. 8 3.1.2 Creating Product Catalog ................................................................................ 9

3.1.2.1 Defining the Basic Data .......................................................................... 9 3.1.2.2 Creating Layout Areas .......................................................................... 10 3.1.2.3 Maintaining Additional Material Texts ................................................... 10

3.1.3 Document Publication .................................................................................... 11 3.1.3.1 Creating the Directory for Document Publication ................................. 11 3.1.3.2 Maintaining Properties of the Default Web Site .................................... 12 3.1.3.3 Copying Pictures to Folder on the Web Server .................................... 12

3.1.4 Document Management ................................................................................ 12 3.1.4.1 Creating Document ............................................................................... 13

3.1.5 Assigning Documents to Product Catalog ..................................................... 13 3.1.6 Index Management System (optional) ........................................................... 14

3.1.6.1 Creating RFC Destination for IMS (optional) ........................................ 14 3.1.6.2 Creating the Search Server Relation (optional) .................................... 14 3.1.6.3 Replication of Catalogs from an ERP Server to a TREX Server (optional) 15

3.2 XCM Configuration for B2B and B2C ..................................................................... 17 3.2.1 Assigning J2EE Admin Role to User Profile .................................................. 17 3.2.2 Generating Authorizations ............................................................................. 17 3.2.3 The Configuration & Component Concept .................................................... 19 3.2.4 Creating the Customer-Specific Configuration .............................................. 19 3.2.5 Configuring the ERP Connectivity ................................................................. 20

3.2.5.1 Creating User WEBLOGIN ................................................................... 20 3.2.5.2 Creating the JCO Component .............................................................. 21

3.2.6 Creating the Shop Component (optional) ...................................................... 22 3.2.7 IPC Component ............................................................................................. 23 3.2.8 Creating the Web Catalog Component ......................................................... 23 3.2.9 Assigning the Components to the Configuration ........................................... 24 3.2.10 Maintaining General Application Settings ...................................................... 25

3.3 User Management .................................................................................................. 26 3.3.1 User Categories in User Management .......................................................... 26


SAP AG Page 5 of 62

3.3.2 Maintaining an Internet User (SU05) ............................................................. 27 3.3.3 Maintaining an Internet User (SU01) with Reference to a Contact Person ... 28

3.3.3.1 XCM Configuration for User Administration .......................................... 28 3.3.3.2 Creating the JCO Component .............................................................. 29 3.3.3.3 Maintaining General Application Settings ............................................. 30 3.3.3.4 Creating the User for User Admin Shop Manager ................................ 31 3.3.3.5 Creating SU01 Internet User for the Customer .................................... 31 3.3.3.6 Creating the Superuser for the Customer ............................................. 32

3.4 B2C Specific User/Customer Settings ................................................................... 33 3.4.1 Creating B2C Reference User ....................................................................... 33 3.4.2 Identifying Relevant ERP Account Groups (SAP ERP) ................................ 34 3.4.3 Creating ERP Reference Customer (SAP ECC) ........................................... 34

3.5 Web Shop Management ........................................................................................ 35 3.5.1 XCM Configuration for the Shopadmin Application ....................................... 35 3.5.2 Creating a Customer-Specific Configuration ................................................. 35 3.5.3 Creating the JCO Component ....................................................................... 36 3.5.4 Creating the Shop Component (optional) ...................................................... 37 3.5.5 Assigning the Components to the Configuration ........................................... 38 3.5.6 Maintaining General Application Settings ...................................................... 38 3.5.7 Creating the User for Web Shop Manager .................................................... 39 3.5.8 Pricing and Price Display (B2B) .................................................................... 40 3.5.9 Creating Web Shop ....................................................................................... 40

3.6 Request for Quotation Settings .............................................................................. 44 3.6.1 Changing Order Type for Request for Quotation .......................................... 44

4 Additional Configuration ................................................................................................ 45 4.1 Setting Order Confirmations via E-Mail .................................................................. 45

4.1.1 Maintaining Output Types.............................................................................. 45 4.1.2 Maintaining Output Determination Procedure ............................................... 46 4.1.3 Creating Output Condition Records .............................................................. 46 4.1.4 Allocating Sales Document Header ............................................................... 47 4.1.5 SAPconnect Configuration for Internet Mail .................................................. 47 4.1.6 Maintaining E-Mail Address for Business Partner ......................................... 48

4.2 Setting Up the Display of Invoices ......................................................................... 49 4.3 Setting Up Shipping Status Tracking ..................................................................... 50

4.3.1 Preparing Tables ........................................................................................... 50 4.3.2 Creating a Vendor ......................................................................................... 51 4.3.3 Creating an Express Delivery Company ....................................................... 51 4.3.4 Changing an Existing Delivery ...................................................................... 54 4.3.5 Creating a Test Entry ..................................................................................... 54


SAP AG Page 6 of 62

5 Appendix ....................................................................................................................... 56 5.1 Administration of Language and Country Settings ................................................ 56 5.2 SAP E-Commerce Administration Console ............................................................ 56

5.2.1 Application Cache Statistics .......................................................................... 57 5.2.2 Catalog Cache Statistics ............................................................................... 58 5.2.3 Application System Cache Statistics ............................................................. 58 5.2.4 Java Connector Pools ................................................................................... 59 5.2.5 Java Connection Sharing .............................................................................. 60 5.2.6 CCMS Heartbeat Customizing ...................................................................... 60 5.2.7 Lean Basket Data Migration to NetWeaver 04 .............................................. 60 5.2.8 Scheduler Administration ............................................................................... 60 5.2.9 Logging .......................................................................................................... 60 5.2.10 Version........................................................................................................... 61

5.3 Modifying and Enhancement of the SAP E-Commerce web application Framework 61 5.4 Restarting single Java Applications using the Visual Administrator ...................... 61


SAP AG Page 7 of 62

SAP E-Commerce for mySAP ERP Configuration Guide

1 Purpose The building block SAP E-Commerce for mySAP ERP contains all configuration steps that are required to set up the following business scenarios: Sales Order Processing Business-to-Business Sales Order Processing Business-to-Consumer

2 Preparation SAP E-Commerce for mySAP ERP is a good option for customers who have no CRM online system, but want to use the advantages of a modern Web shop. This scenario requires basis components like SAP ECC, SAP WAS Java as well as the Java Web Components included in mySAP ERP 2005. Optionally, you can use Internet Pricing and Configurator, TREX as Catalog and Search engine and Web Server for document publication.

2.1 Prerequisites The system landscape including all SAP ECC 6.00 components as described in the SAP Best Practices quick guide and the Java components mentioned above have been set up according to the corresponding Master Guide and Technical Installation Guides.

Optionally: IPC Installation: The IPC is active as soon as you have activated SAP Virtual

Machine Container (VMC). See note 85470. How to configure your SAP Virtual Machine Container (VMC) is described in the configuration guide IPC in SAP E-Commerce for mySAP ERP in http://service.sap.com/erp-inst mySAP ERP 2005 Installation.

TREX Installation: you have installed and configured your TREX Engine as described in the installation guide SAP NetWeaver 2004s Standalone Engine Search and Classification (TREX) in http://service.sap.com/instguidesNW2004s Installation Installation - Standalone Engines & Clients.

Web Server:On the web server the MS Internet Service Manager needs to be installed.

Mandatory: Before using this building block, you need to install all Layer 0 building blocks:

Building Block Description

Layer 0 All layer 0 building blocks


SAP AG Page 8 of 62

2.1.1 SAP Notes Before you begin the installation or configuration, read the relevant SAP Notes. These SAP Notes contain important information on installation of the building block SAP E-Commerce for mySAP ERP. Make sure that you have the most up-to-date version of SAP Notes. You can find the SAP Notes on the SAP Service Marketplace (http://service.sap.com/notes ). SAP Notes that are relevant for SAP E-Commerce for mySAP ERP

SAP Note Number

Release

895332 ERP 2005 SP Stack 2 (12/2005) Release and Information Note

5.0

877887 Installing Patches for CRM Java Components and FSCM BD

5.0

891156 Apply latest patch after installation of SAP E-Commerce 5.0.

5.0

411653 Billing documents are not displayed in the web shop 4.0

3 Basic Configuration 3.1 Product Catalog 3.1.1 General Information about the Product Catalog The Internet product catalog is based on the data from the Product Catalog component in the ERP System. For the Internet Application Component, ERP interprets the product catalog layout in the following way: Layout areas at the first level represent product groups within the shop. Consequently, each ERP product catalog that is to be used in the Internet Application Component must have at least two layout area levels: the highest level for shops, lower levels for product groups. The Internet Application Component shows any long text, picture, or sound file that is assigned to a shop, an item or a layout area. If such multimedia objects are assigned to non-shop layout areas or generic article variants, they will not appear in the Internet Application Component.


SAP AG Page 9 of 62

3.1.2 Creating Product Catalog 3.1.2.1 Defining the Basic Data

Please check the Delta Guide.

Use The following chapter contains very common entries. They are for demonstration purposes only.

Procedure 1. Access the activity using one of the following navigation options: Transaction code WWM1

SAP menu Logistics Materials Management Product Catalog Product Catalog Create

2. Enter the name for your new product catalog. Catalog (Example)

Description (Example)

BP_US Product catalog US

3. Choose Basic Data and make the following entries: Setting Value (Example) Description Auth.group blank Specify if you want to manage access authorizations Un for size blank Specify unit of measure for display in catalog Document Schema A The Document Schema is relevant for the Pricing

Procedure which is used with List-Pricing in SAP E-Commerce for mySAP ERP

Reference Cust. C6120 The Reference Customer is also used for the Pricing Procedure when list prices (Catalog Pricing) are used.

Sales Organization BP01 Specify the Sales Organization your catalog belong to Distr. Channel 01 Specify the Distribution Channel your catalog belong to Division 01 Specify the Division your catalog belong to Display Currency USD Specify the Display Currency your catalog should use

Display prices select Indicator for displaying prices in product catalog maintenance

For the Web Shop management in SAP E-Commerce for mySAP ERP, it is important to create at least one catalog variant. Therefore, create a variant for your catalog.

Setting Value (Example) Description Variant 001 Enter a unique ID for your variant Language EN Specify the language for your variant Currency USD Specify the currency for your variant


SAP AG Page 10 of 62

Setting Value (Example) Description Variant 002 Enter a unique ID for your variant Language DE Specify the language for your variant Currency USD Specify the currency for your variant

Make sure that the display currency in your basic data is used in at least one of your variants.

4. Choose Save.

3.1.2.2 Creating Layout Areas


Procedure 1. Access the activity using one of the following navigation options:

Transaction code WWM2

SAP menu Logistics Materials Management Product Catalog Product Catalog Change

Layout areas can be created either manually, or the classification system could be used to propose a layout hierarchy. Additionally, products out of a material class can be suggested to be included in the layout area, as well as out of layout modules.

2. Choose Layout. 3. Mark the word Layout and choose the Create icon in the application toolbar. 4. Define a name for the new Layout area. 5. Add your products to the new Layout area (for further information, see below). 6. Specify if you want to manage access authorizations for the layout area. 7. Choose Save.

A basis layout area can have up to 7 lower levels but if it contains materials it is not possible to add lower level areas!

Each layout area can have a header, text, or multimedia objects assigned to it. Text and multimedia objects can be assigned to individual items as well. Assigning documents is described in the section Document Management.

3.1.2.3 Maintaining Additional Material Texts

Use You can maintain additional text for each material and for the layout area that you want to display in your web shop. You can copy existing texts from the material master data (if they are maintained), for example, sales texts.






2. Choose Layout. 3. Select a layout area. 4. Select a material, and choose Texts in the application toolbar, or double-click the T

checkbox in the material row. 5. You can maintain the text here or copy it from the material master data. 6. Choose Copy Material Text in the application toolbar. 7. Select the text type you want to copy, for example, Sales and Distribution text. 8. Choose Copy. 9. Choose Back. 10. Choose Save.

In case of creating multiple product catalog versions with different languages, all texts must be maintained in the corresponding languages. With HTML tags, you can change the format of the texts, for example, this word is displayed in bold.

3.1.3 Document Publication 3.1.3.1 Creating the Directory for Document Publication

Use The documents for the product catalog are stored in a separate directory, which must be accessible by HTTP. Therefore, you can create a new directory , which has to be a subdirectory of your HTTP root directory. In case the directory catalog already exists, you can use this directory.

Procedure Web Server Creating the Directory for Document Publication

1. To check whether the directory catalog exists, open the directory default Web site in the file tree structure The MS Internet Service Manager displays the subdirectories and the virtual directories mapped to the default Web site.

2. If you do not find the directory catalog attached to the default Web site, you first have to find out the path of the HTTP root directory.

3. Select the directory Default Web Site, click the right mouse button, and choose Properties.



The Home Directory tab page shows the path to the HTTP root directory in the field Local Path, for example, C:\Inetpub\wwwroot.

4. With the Windows NT Explorer, open the HTTP root directory and create a new subdirectory called catalog.

5. With the Windows NT Explorer, select the directory catalog and choose File Properties.

6. Choose the Web Sharing tab page. 7. Select the option Share this folder, enter Default Web Site in the field Share on, and enter

the alias catalog. 8. Choose the Sharing tab page. 9. Select the option Share this folder, and enter the alias catalog.

3.1.3.2 Maintaining Properties of the Default Web Site

Use After you ensure that the directory catalog exists as a subdirectory of the HTTP root directory, you have to maintain the settings for this directory in the MS Internet Information Server.

Procedure Web Server Maintaining Properties of the Default Web Site

1. In the left window of the Internet Information Server, select the subdirectory catalog. Click the right mouse button, and choose Properties:

2. Choose the Virtual Directory tab page. 3. Ensure that under Access Permissions the Read and Write fields are selected.

3.1.3.3 Copying Pictures to Folder on the Web Server

Please check the Delta Guide.x

Procedure Copy your pictures into the folder on the Web server, which you have specified above.

3.1.4 Document Management Through the document management a connection between the product catalog and the Web server is created. Documents can be any kind of multimedia objects, for example, pictures or sounds. 1. You create a product catalog. 2. You create a directory on the Web server. 3. You put your pictures into the directory on the Web server. 4. You create documents (links with the name of the pictures). 5. You assign the documents to the product catalog.



3.1.4.1 Creating Document


Use In this section you create documents. These documents are the link between the physical files on the Web server and the ERP system.

Procedure For each material you have to run through the following procedure. 1. Access the activity using one of the following navigation options:

Transaction code CV01N

SAP menu Logistics Materials Management Product Catalog Environment Document Management Document Create

2. Enter a Document, for example, . 3. Enter the Document Type L01. 4. Choose Enter. 5. Enter a Description, for example, the name of your material. 6. Choose Create Original. 7. Enter Applic. SIM 8. Enter Original. Enter the file name of your picture. For example, or

. 9. Choose Enter. 10. Confirm the Information Dialog Box. 11. Choose Create Original. 12. Enter Applic. LIM 13. Enter Original . Just enter the file name of your picture. For example, or

. 14. Choose Enter. 15. Confirm the information dialog box. 16. Choose Save.

3.1.5 Assigning Documents to Product Catalog

Use You can assign documents to the Layout Area Level (overview pictures) or to each Material (material pictures). For each material, you have to assign its document.






2. Choose Layout. 3. Select a Layout Area. 4. Select a Material. 5. Double-click on the D checkbox. 6. Enter L01 as type and the requested document number as document. 7. Choose Enter. 8. Choose Documents, if you want to assign a picture on layout area level. 9. Enter L01 as type and the requested document number as document. 10. Choose Enter. 11. Choose Save.

3.1.6 Index Management System (optional) In this section, you can find general information about the settings for the Index Management System (IMS).

The Index Management System itself is part of the Text Retrieval & Information Extraction (TREX.) The installation is part of the system setup and therefore not described here. For more information on the installation of the IMS, please see the installation guide of the TREX. You can find the latest version of this guide in the installation guidelines area on the SAP Service Marketplace: service.sap.com/instguidesNW2004s

3.1.6.1 Creating RFC Destination for IMS (optional) Please refer to the installation guide SAP NetWeaver 2004s Standalone Engine Search and Classification (TREX) Single Host from service.sap.com/instguidesNW2004s

3.1.6.2 Creating the Search Server Relation (optional) Use Before you can publish a product catalog, you have to create a search server relation.




Transaction code SRMO

IMG menu SAP NetWeaver Knowledge Management Settings in the Knowledge Warehouse System Text Retrieval & Information Extraction Define Search Server Relation

2. On the Search Server Relation tab page, check whether an entry with a search server ID IMS_SSR exists. If it does not exist, run steps 2 9.

3. Choose Create SSR. A dialog box appears. 4. In the field Search server relation ID, enter IMS_SSR. 5. Choose Create SSR. 6. In the dialog box that appears, enter the following values

Field name Value Search engine DRFUZZY RFC destination (TCP/IP) Use the same RFC Destination as created in

sm59 during Installation Description: Search Server Relation

7. Save your entries. 8. Select the entry IMS_SSR. 9. Choose Set SSR DEFAULT. 10. In the security prompt, choose Yes. 11. Choose the RFC destinations tab page. 12. For the search server relation IMS_SSR, two entries should exist. One entry is for

indexing (I) and the other one for searching (S). This search server relation establishes an RFC connection. To test the RFC destination for the search server relation, proceed as follows: 13. Select one of the search service relation entries. 14. From the screen area Setting search engine, choose Connection Test. 15. Sometimes you have to restart the transaction SRMO before the connection test works.

Result A message box appears. If the connection was successful, a green traffic light is displayed and the fields Version info for RFC server and Version info for search eng. contain entries.

3.1.6.3 Replication of Catalogs from an ERP Server to a TREX Server (optional)

Use You replicate your product catalog to the TREX server to enhance search functionality and scalability, and to improve system performance for your customers. You replicate your product catalog from your ERP server to the TREX server, using an ABAP Report.

Procedure 1. Access the activity using the following navigation option:



Transaction code ISA_CAT_REPLICATION

You use the transaction ISA_CAT_REPLICATION (ABAP Report ISA_CATALOG_REPLICATION) to replicate product catalogs from your SAP ECC server to a TREX server. The following parameters can be set when replicating a catalog:

Parameter Value Remarks

Catalog ID* BP_US The catalog to be replicated. Variant ID* 001 The catalog variant to be replicated. Search Server Relation*

IMS_SSR The search server relation you configured in transaction SRMO.

Package size for documents*

1.000 The parameter refers to the number of catalog items, and defines the maximum package size that will be replicated to the TREX. If a catalog contains more items then defined with this parameter, several packages will be replicated. You can usually execute the replication with the default value 1000 for this parameter. If, however, you work with very large product catalogs or if you experience performance problems, see SAP Note 837119 for further information.

Read items area-wise

Setting this flag limits the catalog items to be cached in main memory before replicating them to TREX to single catalog areas. You can usually execute the replication without flagging this option which is also the default setting. If, however, you experience performance problems or memory problems, see SAP Note 837119 for further information.

Max. no. of indices per var.

5 This parameter specifies the number of catalog indices on the TREX. Only one index is valid at a time. Choosing a value greater then one may allow to recover a previously replicated catalog. For more information, see SAP Note 837119.

Log level 3 This parameter specifies the detail of information that will be written to the application log when replicating a catalog.

Read long texts checked This flag can be unchecked if no long texts should be displayed for products and catalog areas in the web shop. Deselecting this flag can increase performance during catalog replication and can save memory on the TREX server.

Application for small image

SIM

Application for large image

LIM

* = mandatory parameter 2. For large catalogs, you may wish to execute the replication in the background. Choose

Program Background. 3. The replication result is entered by the system in the application log. The system

automatically displays the application log after each replication when executing the



replication online. You can also display the application log in the ERP system in transaction SLG1, object: ISA Replication.

3.2 XCM Configuration for B2B and B2C

Use Since Version 4.0 of SAP E-Commerce for mySAP ERP, the entire configuration is done by a new configuration application the Extended Configuration Management XCM. XCM provides functionality to configure each component of web application. It is no longer necessary to edit XML files. In this section, only the basic configuration is described that is needed to set up and start SAP E-Commerce for mySAP ERP.

3.2.1 Assigning J2EE Admin Role to User Profile

Use Before you can maintain the XCM, you have to assign to your su01 user a special profile that allows you the access to XCM. Then you can access the XCM with your ECC user and password.


Transaction code SU01

SAP CRM menu Architecture and Technology Administration System Administration User Maintenance Users

2. Enter your User and choose Change. 3. Choose the Roles tab page. 4. Enter additional role SAP_J2EE_ADMIN. 5. Choose Save.

You have to create this user in the client where UME for the J2EE is installed. It is possible that it is another client than the client where you create your master data.

3.2.2 Generating Authorizations

Use Internet User, Web Shop Manager and Super User are created in the following sections. These users need special authorizations. These are the collective roles. You have to check if the single roles within the collective roles are generated. Later, when the users are created, the roles will be assigned.

Roles Users



SAP_ISA_UADM_RFC User admin RFC user SAP_ISA_UADM_MANAGER User admin shop manager SAP_ISA_UADM_SUPERUSER User admin super user SAP_ISA_SHOPMGMT_FULL Web Shop Manager to create Internet User SAP_ISA_B2C_FULL Role for the SU01 B2C users. This role is

assigned to the reference user, not to users directly

SAP_ISA_B2C_RFC Role for the B2C RFC user SAP_ISA_B2B_FULL Full B2B authorizations


Transaction code PFCG

SAP CRM menu Architecture and Technology System Administration User Maintenance Role Administration Roles

2. Run through the following procedure with each of these collective roles: SAP_ISA_UADM_RFC SAP_ISA_UADM_MANAGER SAP_ISA_UADM_SUPERUSER SAP_ISA_SHOPMGMT_FULL SAP_ISA_B2C_FULL SAP_ISA_B2C_RFC SAP_ISA_B2B_FULL

3. In the Role field, enter the role name. 4. Choose Change Role. 5. Choose the Roles tab page. 6. Double-click the single role. Perform the following steps for each single role assigned to

the collective role. 7. Choose the Authorizations tab page. 8. Check if the Authorizations tab page is green. Otherwise generate the Authorizations. 9. Choose Display Change. 10. Choose Change Authorization Data. 11. Choose Organizational levels(sometimes available) 12. Choose Full authorizations. 13. Choose Transfer (Enter). 14. Choose Generate.



3.2.3 The Configuration & Component Concept

Use XCM offers you various configuration possibilities, including the possibility to create customer- specific configurations. Each component, for example JCO, can be assigned to a customer-specific configuration. You can therefore set up your Web Application dynamically with the components you need. For this guide, we want to set up a basic configuration with ERP connectivity.

3.2.4 Creating the Customer-Specific Configuration

Use Check if a customer-specific configuration has already been created by your system administrator. Otherwise, create a new configuration according to the following steps. For example: B2B: B2C:


Web browser XCM B2B URL http://:/b2b/admin/xcm/init.do B2C URL http://:/b2c/admin/xcm/init.do Username Password

2. Select the pre-configured SAP Configuration: XCM Menu Start Application Configurations SAP

r3standardpi

3. Choose Edit. 4. In the field Create customer configuration based on this SAP application configuration,

enter the configuration name for example = (the name of configuration is case-sensitive).

5. Choose Create. 6. Choose Save configuration.

If you are planning to use the TREX search engine for storing your ECC product catalog, choose r3standardpitrex



3.2.5 Configuring the ERP Connectivity

Use The ERP Connectivity depends on two parts. First, you have to create an RFC User in the ERP system which is used by the Web application to connect to the ERP system. Second, you assign that user to the JCO component.

3.2.5.1 Creating User WEBLOGIN

Use In order to set up the connection from the Web application server to the ERP system, you have to define a user with RFC authorization. The user WEBLOGIN is usually required during the installation process of the Web server (for example, SAP J2EE Engine). Check if a different user has already been created by your system administrator. Check if the following fields are maintained. It is important that the email address is maintained, if you want to use the order confirmation via email.



SAP menu Tools Administration User Maintenance Users

2. In the User field, enter WEBLOGIN. 3. Choose Create (F8). 4. Make the following entries:

Address tab page

Last Name WEBLOGIN

Internet Mail A valid e-mail address which appears as sender of order confirmations.

Comm. Method (INT) E-Mail

Function Default user for SAP J2EE Engine

Logon data tab page

User type Service

Password sapphire

Profile tab page

Profiles SAP_ALL and SAP_NEW

Roles tab page



Role SAP_ISA_UADM_RFC

5. Choose Save.

3.2.5.2 Creating the JCO Component

Use You have to define the connectivity to the ERP system. In order to do this, a JCO connection must be set up. JCO stands for Java Connector, and is the interface between the Java based world of Web application and the ABAP-based ERP world. The procedure is the same as for creating a customer-specific configuration.


Web browser Creating the JCO Component B2B URL http://:/b2b/admin/xcm/init.do B2C URL http://:/b2c/admin/xcm/init.do Username Password

2. Access the JCO Component: XCM Menu Start Components Customer jco

3. Choose Edit. 4. Enter a name for the new JCO component in the input field (for example,

), and choose Create. 5. Choose Base Configuration, for example server_connect used for direct connection to

SAP Server. 6. Make the following entries. Copy the entries from the JCO component of the B2B/B2C

Configuration. JCO Access Data

client The client used to log on to the SAP system

lang Language (for example, en )

sysnr System number of SAP system

ashost Application server host name

passwd Password for SAP system. This password is encrypted when it is stored. (for example, sapphire)

user User name (for example, WEBLOGIN)

maxcon Maximum size of SAP Java Connector connection pool.

Jco.client.trace Turns Jco trace on/off.



7. Choose Save configuration. 8. Test the connection. Choose Run test in the Configuration Test dialog box. A window

appears, and the connection data test should be highlighted in green. If it is highlighted in red, an error occurred. In this case, check whether the user name and password of the RFC User and the JCO Component are the same.

3.2.6 Creating the Shop Component (optional) Use Optionally, you can configure your own shop component. You can also use the default for B2B: r3shop_b2b and for B2C: r3shop_b2c. We recommend this option, as you can select them later when you assign the components to the configuration.


Web browser Creating the Shop Component B2B URL http://:/b2b/admin/xcm/init.do B2C URL http://:/b2c/admin/xcm/init.do Username Password

2. Access the JCO Component: XCM Menu Start Components Customer Shop

3. Create your own component by entering a specific name in the input field (for example, , and choose Create.

4. Make the following entries. Name Value Description

Shopscenario B2B

Shop scenario, for example, B2B, B2C, OOB, HOM. Only those shops for which a scenario matches the entry given here, appear in the shop list and can be started

Object-Path For example:

D:\CRM4.0\shopadmin\r3shop

File system path that contains the ISA ERP shops

The file system path you use for shop data upload from the file system to the J2EE DB. This is only relevant if you perform an upgrade from releases 3.1 or 4.0. Please use the administration area of the shop management application to perform the upload.



documentsearch.name SearchCriteria_B2B_Sales

Define the name of the document search description according to file \xcm\sap\modification\generic-searchbackend-config.xml, which will be used for this application.

defaultShopId Shop Id for default shop for B2B, B2C and CCMS Heartbeat

5. Choose Save configuration.

3.2.7 IPC Component

Use

As of CRM 5.0, the Internet Pricing and Configurator 7.0 is a component of the Application Platform (AP). Compared to the previous release (IPC 4.0), a significant change has been made by switching the technology to the SAP Virtual Machine Container (VMC), which is part of the SAP Web Application Server (SAP Web AS) and SAP NetWeaver 2004s. The IPC was moved to the SAP Web AS in order to use the VMC. For IPC Configuration please use Document IPC in SAP E-Commerce for mySAP ERP from service.sap.com.

3.2.8 Creating the Web Catalog Component

Use This component contains general information about the Web catalog. For example, the location of the image files is defined here.


Web browser Creating the Web Catalog Component B2B URL http://:/b2b/admin/xcm/init.do B2C URL http://:/b2c/admin/xcm/init.do Username Password

2. Access the Web catalog component. XCM Menu Start Components Customer webcatalog

3. Create your own component by entering a specific name in the input field (for example, ), and choose Create.

4. Make the following entries: Name Value Description



Name Value Description

imageserver The directory you have created above.

For example: http://://

This URL describes the server directory to which images are published. In the application, this URL will be concatenated with the original entry out of the Document Management System in the ERP for each image to build the full URL for the html 'img' tag.

itemPageSize 5 The number of items to be displayed on one screen in the item list. Set this to 0 (=zero) to display all items on one screen.

numPageLinks 10 The number of page links to be displayed in the search results page

preventIPCPricing false Defines whether IPC pricing in the catalog should be prevented or not.

maxSearchHits 10000 Parameter to control the number of maximum search results to be retrieved


Result Afterwards, you can access your new component as a subnode of Web catalog: XCM Menu Start Components Customer webcatalog

3.2.9 Assigning the Components to the Configuration

Use All the components created and maintained must be assigned to the customer-specific configuration. Then the web application is able to determine all components that should be used in your specific configuration.


Web browser XCM B2B URL http://:/b2b/admin/xcm/init.do B2C URL http://:/b2c/admin/xcm/init.do Username



Password

2. Access your customer-specific configuration: XCM Menu Start Application Configurations Customer

3. Choose Edit. 4. Choose Display Advanced Settings. 5. Check or make the following entries. Leave the other entries as they are.

Param.Name Value Component

jcodata JCO

ipcjcodata JCO

ipcdata ipcdefault IPC

shopdata

B2B: r3shop_b2b or

B2C: r3shop_b2c or

SHOP

Usertype

B2B: R3_SU05_Customer_LoginCustomerNo

B2B: R3_SU01UserContactPerson (general recommended )

B2C: R3_SU05_Customer_LoginEmail

B2C: R3_SU01Customer_LoginEmail (general recommended)

Depending on how you want to access the webshop you make here the decision if you are using su01 or su05 users

webcatdata webcatalog

6. Set the checkbox Active Configuration. 7. Check the checkbox Default Configuration. Otherwise, you have to add

?scenario.xcm=< YOUR_CONFIGURATION > to your Webshop URL. 8. Choose Save Configuration.

3.2.10 Maintaining General Application Settings

Use You must define specific parameters for the web application, regardless if you are using SSL or not.




Web browser XCM B2B URL http://:/b2b/admin/xcm/init.do B2C URL http://:/b2c/admin/xcm/init.do Username Password

2. To carry out the activity, open the standard SAP Configurations: XCM Menu Start General Application Settings Customer b2b

b2bconfig XCM Menu Start General Application Settings Customer b2c

b2cconfig

3. Choose Edit. 4. Select false for parameter SSLEnabled 5. Choose Save. 6. Restart your application. 7. To restart, access the activity using the following navigation option:

Web browser SAP NetWeaver Administrator B2B URL http://:/nwa SAP NetWeaver Administrator Menu

System Management Administration Applications

8. Search for your application (for example, B2B or B2C). 9. Mark your application in the Application List. 10. Stop and start your application use the application detail Status tab page.

3.3 User Management Users require an active Internet user to log on to the Web shop of the web application. You need Internet users for the B2B and B2C scenarios and for the shopadmin application to create your Web shop. You can create and maintain Internet users for your Web-based applications in the following ways:

In your ERP backend system For all ERP E-Commerce applications.

n the Web-based User Management application For B2B ERP E-Commerce applications only

3.3.1 User Categories in User Management In the XCM Application of your B2B and B2C application, you can select the user type for your Internet user. For example, you can select that the B2B user logs on to the Web shop with his or her customer number.



Possible user categories

Usertype B2B B2C Shopadmin R3_SU01User X X

R3_SU01UserStandalone X X

R3_SU01UserContactPerson X

R3_SU05Customer_LoginCustomerNo X

R3_SU05ContactPerson_LoginContact PersonId

X

R3_UMESU01User X

R3_UMESU01UserContactPerson X

R3_UMESU01UserStandalone X X

R3_SU01Customer_LoginEmail X

R3_SU05Customer_LoginEmail X

Two options are described below:

Usertype R3_SU05Customer_LoginCustomerNo is defined in the section Maintaining an Internet User in this document

Usertype R3_SU01UserContactPerson is defined in the section Maintaining an Internet User (SU01) with reference to a contact person in this document.

Corresponding to your chosen option, maintain your XCM configuration of B2B application.

3.3.2 Maintaining an Internet User (SU05)

This is another option to create an internet user. Generally, it is recommended to use su01 user, therefore skip this chapter.

Use This transaction allows you to create an SU05 user with reference to a customer and to maintain user data (passwords, for example) in a table. Internet users are identified by: User name and User category The Internet user information is client-dependent and is an extension of the user master record. When the Internet user identifies themselves later on in the Web applications, this information is checked in table BAPIUSW01. Unauthorized users are prevented from accessing the applications.





2. Enter the user ID and user category KNA1. 3. Choose the following functions: Create The system returns the initial password for the Internet user.

Note the password if you want to pass it on to the user. Otherwise, choose Change Password to assign the user a new password. Assign the created ID and password to the corresponding user.

Change Enter a new user ID or change the validity period. Delete Internet user is deleted after a confirmation is made.

Lock/Unlock A user is also locked if they tried to log on twelve times Change Password Enter the new password twice. Initialize A new password is generated.

3.3.3 Maintaining an Internet User (SU01) with Reference to a Contact Person

3.3.3.1 XCM Configuration for User Administration

Use Before you create a user, you have to define your customer configuration and set up the parameters for the user administration. If you are using transaction SU01 to create a B2B user, make sure that you change your XCM settings for B2B to user type R3_SU01UserContactPerson or R3_SU01User.


Web browser XCM Configuration for User Administration URL http://:/isauseradm/admin/xcm/init.do Username Password

2. Select the pre-configured SAP configuration:

XCM Menu Start Application Configurations SAP isar3useradmStandard

3. Choose Edit. 4. Enter the configuration name in the field Create customer configuration based on this

SAP application configuration, for example, (the name of configuration is case- sensitive).

5. Choose Create. 6. Set your configuration as default configuration.



7. Assign a value to a configuration parameter jcodata by selecting the appropriate value from the dropdown list.

If the parameter jcodata does not exist, you can create it in the folder Components Customer jco. This is described below.


3.3.3.2 Creating the JCO Component


Web browser Creating the JCO Component URL http://:/isauseradm/admin/xcm/init.do Username Password

2. Access the JCo Component: XCM Menu Start Components Customer jco

3. Choose Edit and enter a name for the new JCO component in the input field (for example, ), and choose Create.

4. Choose your base configuration, for example server_connect.

You can connect to an SAP system application server directly (server_connect), or using load balancing via a message server (group_connect).

5. Enter the required data, for example: JCO Access Data











7. Test the connection. Choose Run test in the Configuration Test dialog box. A window appears and the connection data test should be highlighted in green. If it is highlighted in red, an error occurred. In this case, check whether the user name and password of the RFC User and the JCO Component are the same.

8. Assign your jco component to application configuration as mentioned in the section XCM Configuration for User Administration of this document.

3.3.3.3 Maintaining General Application Settings

Use You must define specific parameters for web application regardless if you are using SSL or not.


Web browser Maintaining General Application Settings URL http://:/isauseradm/admin/xcm/init.do Username Password

2. To carry out the activity, open the standard SAP Configurations: XCM Menu Start General Application Settings Customer

isauseradm isauseradmconfig 3. Choose Edit. 4. Select false for parameter SSLEnabled 5. Choose Save. 6. Restart your application. 7. To restart, access the activity using the following navigation option:

Web browser SAP NetWeaver Administrator B2B URL http://:/nwa SAP NetWeaver Administrator Menu


8. Search for your application (for example, isauseradm). 9. Mark your application in the Application List. 10. Stop and start your application by using the application detail Status tab page.



3.3.3.4 Creating the User for User Admin Shop Manager

Use In order to create superusers and Web shop users for all companies, you need a user with the authorization role User admin Shop Manager SAP_ISA_UADM_MANAGER. You can add this role to your su01 user, or you can create new one.

Procedure 1. Access the activity using the following navigation options: Transaction code SU01 SAP menu Tools Administration User Maintenance Users

2. In the User field, enter USERADMIN. 3. Choose Create (F8). 4. Enter the following data:

Address tab page

Last Name User Admin Shop Manager

E-Mail A valid e-mail address which appears as sender of user and password

Comm. Method E-Mail

Logon data tab page

Alias

The alias is required for the determination of the User by logon to the Web-Management.

User type Dialog

Password Initial (at the first logon, change password to welcome)

Roles tab page

Role SAP_ISA_UADM_MANAGER

5. Choose Save.

3.3.3.5 Creating SU01 Internet User for the Customer

Please check the Delta Guide. For the SAP Best Practices scenario, use this meathod to create an internet user.



Use This transaction allows you to create su01 user with reference to a customer, and to maintain user data (for example, passwords) with a web user interface. Later, the contact person of the customer can log in to the web shop with this user.

Procedure 1. Access the activity using the following navigation options: Web browser

Creating a SU01 Internet User for the Customer

URL http://:/isauseradm/useradmin/init.do?scenario.xcm=

2. Log on to the Web User Management with the above-created user and password (for example, Web shop manager user and password).

3. Choose Create new users.

You can create an Internet user for a contact person that already exists in the system, or you can create a new internet user and contact person with the Web user interface.

4. Choose Create New User for Existing Contact Person. 5. Enter the Company. 6. Choose Go. 7. Select the Contact Person, and choose Copy to create a new internet user. 8. Enter the User ID*. With this user ID, the contact person will log on to the Web shop. 9. Assign the authorization, select Full B2B Authorizations, and choose the > button. 10. Choose Continue. 11. Choose Create.

Result You receive a new initial password and have to pass on the access data to the Internet user. The first time the Internet user logs onto the Web shop, the user will have to change the password.

3.3.3.6 Creating the Superuser for the Customer

Use In order to create or maintain a superuser on the customer side, you need a user admin shop manager with the authorization role SAP_ISA_UADM_MANAGER. A Superuser can create superusers for companies to which he or she is assigned, and create Web shop users.



Procedure 1. Access the activity using the following navigation options: Web browser

Creating a Super User for the Customer

URL http://:/isauseradm/useradmin/init.do?scenario.xcm=

2. Log on to the Web user management with the above-created user and password (for example, Web shop manager user and password).

3. Choose Display and Change Existing Users. 4. Enter the User ID. 5. Choose Change. 6. Choose Create New User And New Contact Person. 7. Enter the data, such as User ID, First Name and Last Name, E-mail of the user, select

via the dropdown list the Form of Address / Title 8. Assign the authorization, select Full B2B Authorizations and Super User for User

Management, and choose the > button. 9. Choose Continue. 10. Enter the communication data: language, telephone, fax. 11. Choose Create.

Result You receive a new initial password and have to pass on the access data to the superuser. The first time of log on to the Web shop, the superuser must change the password.

3.4 B2C Specific User/Customer Settings 3.4.1 Creating B2C Reference User

Use In order to create a new B2C Customer, you need a reference user with the authorization roles SAP_ISA_B2C_RFC and SAP_ISA_B2C_FULL.

Procedure 1. Access the activity using the following navigation options: Transaction code SU01


2. In the User field, enter B2CREFUSER. 3. Choose Create (F8). 4. Enter the following data:

Address tab page



Last Name B2C Reference User

Logon data tab page

User type Service


Roles tab page

Role SAP_ISA_B2C_RFC

Role SAP_ISA_B2C_FULL

5. Choose Save.

3.4.2 Identifying Relevant ERP Account Groups (SAP ERP) Use In this activity, you identify an account group with internal number assignment. The reference business partner must be created within this account group.

Procedure 1. Access the activity using one of the following navigation options: Transaction code OVT0

IMG menu Logistics General Business partners Customers Control Define account groups and field selection for customer

2. Select your relevant customer groups. 3. Choose Details (F2). 4. An overview table of the number ranges appears.

Select the field Number range and choose F4 to get the interval for this number range. In this table, the External field indicates whether the number range is internal or external.

5. Write down the account group in which the ERP reference customer is going to be created. For example, you can use account group DEBI to create your reference customer.

3.4.3 Creating ERP Reference Customer (SAP ECC) Use You have to create a customer master record that can be used as reference customer. This customer must have consistent sales area data.

Do not choose an existing customer as reference business partner. Create the reference customer as sold-to-party with internal number assignment.



Procedure 1. Access the activity using one of the following navigation options: Transaction code XD01

SAP menu Logistics Logistics Execution Master Data Partner Customer Create Total

2. Create a new customer master record, and maintain all relevant data. You can also copy this business partner from an existing business partner where typical sales area data is already maintained.

3. In the section Creating Web Shop in this document, enter your reference customer on the Transactions tab page of your Web shop.

3.5 Web Shop Management

3.5.1 XCM Configuration for the Shopadmin Application

Use Web shops are maintained by a Web-Application called Shopadmin. The Web shop can be used by the B2B or the B2C scenario. Before you can create a Web shop with the shopadmin application, you have to configure the XCM shopadmin application. You need to create a customer-specific Web shop configuration and later assign the corresponding components (JCO) for the Web shop.

3.5.2 Creating a Customer-Specific Configuration

Use A new customer-specific configuration is created, to which the components can later be assigned.

Procedure 1. Access the activity using the following navigation options:

Web browser Creating a Customer-Specific Configuration URL http://:/shopadmin/admin/xcm/init.do Username Password

2. To carry out the activity, open the standard SAP Configurations: XCM Menu Start Application Configurations SAP r3shop

3. Select the default configuration for r3shop, and choose Edit. 4. Enter a name for the new configuration in the input field.



5. Choose Create. 6. Maintain Description and mark this configuration as default configuration and active

configuration. 7. Choose Save.

Result The new configuration has been created and can be accessed via: XCM-Menu Start Application Configurations Customer

3.5.3 Creating the JCO Component

Use Next, you have to define the connectivity to the ERP System. In order to do this, a JCO connection must be set up. JCO stands for Java Connector, and is the interface between the Java based world of Web Application and the ABAP-based ERP world. The procedure is the same as for creating a customer-specific configuration.


Web browser Creating the JCO Component URL http://:/shopadmin/admin/xcm/init.do Username Password

2. Access the JCO component: XCM Menu Start Components Customer JCO

3. Choose Edit and enter a name for the new JCO component in the input field (for example, ) and choose Create.

4. Make the following entries. Copy the entries from the JCO component of the B2B/B2C configuration.

JCO Access Data










Jco.client.trace Turns JCO trace on and off.

5. Choose Save configuration. 6. Test the connection. Choose Run test in the Configuration Test dialog box. A window

comes up and the connection data test should be highlighted in green. If it is highlighted in red, an error occurred. In this case check whether the user name and password of the RFC User and the JCO Component are the same.

Result Afterwards, your can access your new component as a subnode of JCO: XCM-Menu Start Components Customer JCO

3.5.4 Creating the Shop Component (optional) Use Optionally, you can configure here additional settings used by the selected shop type.


Web browser Creating the Shop Component URL http://:/shopadmin/admin/xcm/init.do Username Password

1. Access the shop component: XCM Menu Start Components Customer Shop

2. Create your own component by entering a specific name in the input field (for example, ), and choose Create.

3. Make the following entries. Name Value Description

Object-Path For example

D:\CRM4.0\shopadmin\r3shop

File system path that contains the ISA ERP shops

The file system path you use for Shop Data upload from the file system to the J2EE DB. This is only relevant if you perform an upgrade from releases 3.1 or 4.0. Please use the administration area of the shop management application to perform the upload.




3.5.5 Assigning the Components to the Configuration

Use All the components created and maintained must be assigned to the customer-specific configuration. The application is then able to determine all components that should be used in your specific configuration.

Procedure 1. Access your customer-specific configuration:

XCM Menu Start Application Configurations Customer

2. Choose Display advanced settings. 3. Check or make the following entries. Leave the other entries as they are.

Param.Name Value Component

jcodata JCO

shopdata SHOP

Usertype R3_SU01_User

4. Check the checkbox Default Configuration. Otherwise you have to add ?scenario.xcm=< YOUR_CONFIGURATION > to your Webshop URL.

5. Choose Save Configuration.

3.5.6 Maintaining General Application Settings

Use The first step is to define parameters specific to the shopadmin application.


Web browser URL http://:/shopadmin/admin/xcm/init.do Username Password

2. To carry out the activity, open the standard SAP Configurations: XCM Menu Start General Application Settings Customer

shopadmin shopadminconfig 3. Choose Edit. 4. Select false for parameter SSLEnabled 5. Choose Save.



6. Restart the J2EE Engine or shopadmin application. To restart the shopadmin application, call SAP NetWeaver Administrator using http://:/nwa.

SAP NetWeaver Administrator Menu


7. Search for your application (for example, shopadmin) 8. Mark your application in the Application List. 9. Stop and start your application by using the application detail Status tab page.

3.5.7 Creating the User for Web Shop Manager

Use In order to create or maintain a Web shop, you need a user with the authorization role Full ShopMgmt autohorizationsr SAP_ISA_SHOPMGMT_FULL. You can add the role to your su01 user, or you can create new one.

Procedure 1. Access the activity using the following navigation options: Transaction code SU01


2. In the User field, enter WEBADMIN. 3. Choose Create (F8). 4. Enter the following data:

Address tab page

Last Name Web Shop Manager

E-Mail A valid e-mail address which appears as sender of user and password

Comm. Method E-Mail

Logon data tab page

Alias WEBADMIN

The alias is required for the determination of the User by logon to the Web management.

User type Dialog


Roles tab page



Role SAP_ISA_SHOPMGMT_FULL

5. Choose Save.

3.5.8 Pricing and Price Display (B2B) When you create a purchase order or order template, catalog prices are used. Catalog prices can be list prices or prices defined by the IPC. ERP pricing takes place after the order has been prepared or simulated. You can then either place the order, or continue processing the order. If the catalog prices are defined by the IPC, you can use customer-specific prices. The calculation schema for IPC is determined during ERP Customizing using the order type, the customer and the sales area. If you are not using the IPC, prices are taken from the ERP catalog.

3.5.9 Creating Web Shop


Use The Web shop allows you to define which products you want to sell in the Business-to-Business and Business-to-Consumer scenario of SAP E-Commerce for mySAP ERP. You specify the contents in the product catalog, which also forms the basis of the Web shop. You maintain the shop itself, for example which transactions, functions, and product catalog you wish to offer.

Procedure Web browser Shopadmin URL http://:/shopadmin/shopadmin/init.do?language= :: host and port

: Logon language, for example en or de

1. Log on to Web shop management with your Web shop manager user. 2. Choose Create New Shop for a specific scenario, for example B2B/B2C. 3. You can edit the following entries: Field Value

(Example) Description

Shop ID BP_US_01 Enter an ID for the shop. The shop ID can only be assigned once.

Description Best Practices US

Enter a description for the Web shop.

General Information tab page General Settings Language EN Enter the language for the shop in ISO code. You

can only view those shops with the same language



as the logon language. Country US Enter the country for the shop. The country and the

language are used to convert currency and date formats. The formats are determined using standard Java settings for the combination of country and language. You must enter the country in ISO code.

Departure Country US Enter the departure country for tax determination. This is relevant for pricing display in the catalog if the catalog pricing procedure contains taxes and if you use IPC for catalog pricing.

Country Group 0002 Enter the ERP country group. This is a list of countries that are permissible for a shop.

Address Format American Determine address format. Addresses can have different formats; in Germany, for example, the order is street, house number, ZIP code and town and in the USA, it is house number, street, town, ZIP code.

IPC active Activate this setting if you want to use IPC either for configuration or pricing in catalog or shopping basket.

User Management Reference User B2CREFUSER Enter your su01 B2C reference user, created in the

section Creating B2C Reference User. This is relevant for B2C when an SU01 user scenario is active. During the registration process, newly created users are created with the reference user and later get their authorizations from there.

Usage Business Scenario B2B/B2C Type of scenario for which the web shop is to be

used. You can choose either B2C, B2B, or both. Catalog tab page Product Catalog Currency USD Enter the currency of the catalog. This is also the

currency of the catalog variant from ERP. Internal catalog exists

checked With this setting, you can specify if an internal (ERP) catalog exists.

Display Catalog Views

If you set this flag, the information of the customer's catalog view is read and interpreted when the catalog is displayed. You can leave this field empty.

Catalog BP_US Enter the ERP catalog ID for the shop catalog. Catalog Variant 001 The variant for the catalog (entered above) to be

used in the shop Controlling Price Determination in the Catalog

IPC Via IPC: Price determination is carried out by the IPC. List prices are read from the index server. If there is no index server available, they are read from the ERP System.



Enable Cross-Selling

Set this flag if you want to enable the Cross-Selling function in ERP E-Commerce. Also check the ERP IMG Customizing in Sales And Distribution Basic Functions Cross-Selling

Transactions tab page Order Enable Templates checked Specify whether or not to use order templates.

When selected, you can search for and make use of order templates when creating an order in the B2B shop. You can also copy items from the order templates to the shopping basket. Alternatively, you can create your own order template in the B2B shop. When the Order templates checkbox is not selected, you can no longer search for order templates when creating an order in the B2B shop. You can no longer copy items from the order templates to the shopping basket. You can only use order templates when a JDBC database is connected to the web application.

R/3 Order Type TA Enter the ERP transaction type for orders generated from the web application.

Header Text ID 0001 Shorthand for the use of user-defined texts at header level

Item Text ID 0001 Shorthand for the use of user-defined texts at item level

Sales Organization BP01 Enter the sales organization for orders Distribution Channel 01 Enter the distribution channel for orders Division 01 Enter the division for orders Shipping Conditions Enter the ERP keys of the shipping conditions you

want to have available in the shop, separated by commas. If you leave this field blank, all shipping conditions from ERP will be displayed.

Reason for Rejection when Canceling Order Items

05 Shorthand for the reason for cancellation defined in the ERP system

Delivery Block Enter here the delivery block (technical ERP name: LIFSK) that should be written in the ERP order during order creation. You can leave this field empty.

Order Type Enter here the purchase order type (technical ERP name: BSARK) that should be written in the ERP order during order creation. You can leave this field empty.

Reference Customer filled Enter the reference customer you would like to use as a template when a new B2C user is registered. For more information on customer creation, see the section Creating ERP Reference Customer (SAP



ECC) in this document. Business Partner for Cash on Delivery

filled This field is only valid for payment type Cash on Delivery. This business partner is used as the payer partner when an order is created. For more information on customer creation, see the section Creating ERP Reference Customer (SAP ECC) in this document.

Allow Sales Document Change

checked Causes sales documents to be changeable, if their ERP status allows it.

Enable Contract Display

checked Enables contracts to be displayed.

Follow-on Documents

Display Invoices, Down Payments and Credit Memos

checked Here, you can decide if you want to display and search for these document types.

No Tracking with Express Delivery Companies (XSI)

not checked Here, you can decide if you want to switch off tracking with express delivery companies (XSI)

Quotations Enable Quotation Creation (B2B application only)

checked Also enables a quotation to be drawn up and a quotation to be searched for (in B2B scenario only)

R/3 Order Type AF Document type when a quote is requested, for example, AF. This value is defined in Customizing

Create Inquiry Text Items for Unknown Materials

checked If an external product catalog is linked via the OCI interface, it is possible to take over products from this external catalog as a user-defined text into ERP, even if these products are not entered in the ERP product catalog.

Payments By Invoice Possible checked Payment by invoice is possible By Cash on Delivery possible

checked Payment by cash on delivery is possible

By Credit Card Possible

checked Payment by credit card is possible

Payments: Preassignment: Payment

By Invoice Determination of the standard setting for the payment method; only one method is possible.

Customers tab page Quotation and Order Management for Internal Users / Business-On-Behalf for Channel Partners activated

Not checked With this setting, you can determine if the scenario for internal users or the scenario Business-on-Behalf for channel partners will be activated.



3.6 Request for Quotation Settings 3.6.1 Changing Order Type for Request for Quotation

Use In this activity, you identify the order type for your quotation and change the proposed pricing date. Enter todays date in this field.

Procedure 1. Access the activity using one of the following navigation options: Transaction code VOV8 IMG menu Sales and Distribution Sales Sales Documents Sales

Document Header Define Sales Document Types

2. Select Sales Document Type IN.

3. Select for the Prop. f. Pricing Date blank (proposal based on todays date). 4. Choose Save.



4 Additional Configuration Use The Best Practices Configuration Guide contains the information necessary to set up the Business Scenario with SAP E-Commerce for mySAP ERP. The guide also has the intention to enable you to start a Web shop as fast as possible. In this section, some special features are described which are not essentially necessary to set up or run the standard implementation of SAP E-Commerce for mySAP ERP.

4.1 Setting Order Confirmations via E-Mail In common e-commerce environments, it is possible to send an order confirmation via e-mail. This is the case in SAP E-Commerce for mySAP ERP. Here, the SAP ECC message determination is used to check that an order has been created. Afterwards, an e-mail with the order confirmation as attachment is sent to the purchaser. For more information, see the SAP E-Commerce for mySAP ERP Bus. Scenario Config Guide 5.0 in service.sap.com/erp-inst mySAP ERP 2005 Installation

4.1.1 Maintaining Output Types

Use In this activity, you set up the message determination for sales documents, messages and text elements.

Procedure 1. Access the activity using one of the following navigation options: Transaction code V/30

IMG menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Sales Documents Maintain Output Types

2. Create a new output type by copying the entry BA00 Order Confirmation. Name it YBAI

3. Maintain the entry YBAI by selecting the corresponding entry in the table.

4. On the General Data tab page, enter the access sequence 0002 (Order Type). 5. Choose only copy entry in the upcoming dialog box, Specify object to be copied. 6. Select YBAI.

7. Choose Processing routines.

8. Choose New Entries.

9. Make the following entries: Output Type

Application Transport-Medium

Program FORM Routine

Form



YBAI V1 5 RVADOR01 ENTRY RVORDER01

10. Choose Save.

4.1.2 Maintaining Output Determination Procedure

Use The output type has to be assigned to the output procedure.

Procedure 1. Access the activity using the following navigation options: Transaction code SPRO

IMG menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Sales Documents Maintain Output Determination Procedure

2. Select the procedure V10000 (Order Output). 3. Choose Control Data.

4. Choose New Entries.

5. Make the following entries: Step Cntr Ctyp Requiremnt Next available 1 YBAI 2

6. Choose Save.

4.1.3 Creating Output Condition Records

Use Condition records for order confirmation have to be created and assigned to the output type.

Procedure 1. Access the activity using one of the following navigation options: Transaction code VV11

SAP menu Logistics Sales and Distribution Master Data Output Sales document Create

2. Enter the output type YBAI

3. Choose Enter.

4. Make the following entries: Sales Doc Name Funct Medium Date/Time Language



Type OR Standard order SP 5 4 EN

5. Select your new entry and click on Communication (you may have to use the transaction VV12 to change your new entry).

6. Enter the following data in the specified fields: Comm.strategy CS01 Output Device LP01 Print immediately marked Release after output marked SAP Cover Page Do Not Print Cover Page Text Order Confirmation

7. Choose Save.

4.1.4 Allocating Sales Document Header

Use Now the output type has to be assigned to the Sales Document type. Check whether an entry for the Sales Document OR already exists.

Procedure 1. Access the activity using one of the following navigation options: Transaction code V/43

IMG menu Sales and Distribution Basic Functions Output Control Output Determination Output Determination Using the Condition Technique Maintain Output Determination for Sales Documents Assign Output Determination Procedures Allocate sales document header

2. Check whether an entry for the Sales Document OR already exists.

3. Create or maintain the entry as follows: SaTy Out.pr Output Type OR V10000 YBAI

4. Choose Save.

4.1.5 SAPconnect Configuration for Internet Mail

Use SAPconnect provides a standard interface for external communication, which supports sending using telecommunication services, such as faxing, pagers (SMS), Internet and X.400, as well as sending to printers and between several SAP Systems. It enables external communication components to be connected to the SAP System.



As of Release 6.10, SAPconnect also provides a direct connection to the Internet using the SMTP plug-in of the Web application server. This enables you to send messages directly to Internet, fax, and paging addresses without using an additional external communication system.


Transaction code SCOT

Here you should always find an already generated SMTP node labeled like SMTP Mail Server. If you find more than one SMTP node, it is an error!

2. On the SAPconnect: Administration (system status) screen, double-click the SMTP node. 3. In the following dialog box enter the following values:

Field Name Field Entry General information Description Mail Server Hours/minutes --/30 Node in use

SMTP Connection Mail Host Mail Port 25

Code Page 1100 SAP Internal like ISO 8859-1 4. Under portion Supported address types, click on the Set button next to the Internet

checkbox. 5. Enter * in the first row of the Address area. 6. Choose Continue. 7. Back on the SAPconnect: Administration (system status) screen choose Settings

Default Domain from the menu. 8. In the dialog box enter your SMTP default domain, for example,

..com, and continue.

Ask your system administrator for the right domain.

4.1.6 Maintaining E-Mail Address for Business Partner

Use The purpose of this activity is to maintain the e-mail address in the master data of the required Business Partner.




Transaction code XD02

SAP menu Logistics Sales and Distribution Master Data Business Partner Customer Change

2. Select the required Business Partner, for example, C6120. 3. Be sure to be in change mode (choose Switch Between Display and Change) 4. On the Address tab page, enter the e-mail address.

Field Name Field Entry Communication E-Mail

5. Choose Save.

4.2 Setting Up the Display of Invoices

Use This procedure enables logged on business partners to inform themselves in the Web shop about the status of invoices.

Prerequisites You have installed SAP E-Commerce for mySAP ERP.

Procedure 1. Access the activity using one of the following navigation options: Transaction code SPRO

IMG menu Sales and Distribution Billing Lists Set Updating of Partner Index

2. Enter the role of the sold-to party.

TrG Funct Name 7 SP Sold-to party

3. Save your entries. 4. Call transac