EWM

SAP ERP 6.0 EhP3

August 2008

English

SAP E-Commerce withSAP ERP (220)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices SAP E-Commerce with SAP ERP (220): Configuration Guide

Copyright

© Copyright 2008 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, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, 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 2 of 67


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.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents1 Purpose........................................................................................................................... 7

2 Preparation...................................................................................................................... 7

2.1 Prerequisites.............................................................................................................7

2.1.1 SAP Notes..........................................................................................................7

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...................................................................................8

3.1.2.1 Defining the Basic Data...............................................................................8

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 Setting of TCP Port....................................................................................12

3.1.3.4 Copying Pictures to Folder on the Web Server..........................................13

3.1.4 Document Management...................................................................................13

3.1.4.1 Creating Document....................................................................................13

3.1.5 Assigning Documents to Product Catalog........................................................14

3.1.6 Index Management System (optional)..............................................................14

3.1.6.1 Creating RFC Destination for IMS (optional)..............................................15

3.1.6.2 Creating the Search Server Relation (optional).........................................15

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

3.1.6.4 Specifying the Address of the TREX Name Server....................................18

3.2 XCM Configuration for B2B and B2C......................................................................18

3.2.1 Assigning J2EE Admin Role to User Profile.....................................................18

3.2.2 Generating Authorizations................................................................................19

3.2.3 The Configuration & Component Concept........................................................20

3.2.4 Creating the Customer-Specific Configuration.................................................20

3.2.5 Configuring the ERP Connectivity....................................................................21

3.2.5.1 Creating User WEBLOGIN........................................................................21

3.2.5.2 Creating the JCO Component....................................................................22

3.2.6 Creating the Shop Component (optional).........................................................23

3.2.7 IPC Component................................................................................................24

3.2.8 Creating the Web Catalog Component.............................................................24

3.2.9 Creating UI Component....................................................................................26

3.2.10 Assigning the Components to the Configuration..............................................28



3.2.11 Maintaining General Application Settings.........................................................29

3.3 User Management..................................................................................................30

3.3.1 User Categories in User Management.............................................................30

3.3.2 Maintaining an Internet User (SU05)................................................................31

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

3.3.3.1 XCM Configuration for User Administration...............................................32

3.3.3.2 Creating the JCO Component....................................................................33

3.3.3.3 Maintaining General Application Settings..................................................34

3.3.3.4 Creating the User for User Admin Shop Manager.....................................34

3.3.3.5 Creating SU01 Internet User for the Customer..........................................35

3.3.3.6 Creating the Superuser for the Customer..................................................36

3.4 B2C Specific User/Customer Settings....................................................................37

3.4.1 Creating B2C Reference User..........................................................................37

3.4.2 Identifying Relevant ERP Account Groups (SAP ERP)....................................38

3.4.3 Creating ERP Reference Customer (SAP ERP)...............................................38

3.5 Web Shop Management.........................................................................................39

3.5.1 XCM Configuration for the Shopadmin Application..........................................39

3.5.2 Creating a Customer-Specific Configuration....................................................40

3.5.3 Creating the JCO Component..........................................................................40

3.5.4 Creating the Shop Component (optional).........................................................41

3.5.5 Assigning the Components to the Configuration..............................................42

3.5.6 Maintaining General Application Settings.........................................................43

3.5.7 Creating the User for Web Shop Manager.......................................................43

3.5.8 Pricing and Price Display (B2B).......................................................................44

3.5.9 Creating Web Shop..........................................................................................45

3.6 Request for Quotation Settings...............................................................................48

3.6.1 Changing Order Type for Request for Quotation..............................................48

4 Additional Configuration................................................................................................49

4.1 Setting Order Confirmations via E-Mail...................................................................49

4.1.1 Maintaining Output Types................................................................................49

4.1.2 Maintaining Output Determination Procedure..................................................50

4.1.3 Creating Output Condition Records..................................................................50

4.1.4 Allocating Sales Document Header..................................................................51

4.1.5 SAPconnect Configuration for Internet Mail.....................................................52

4.1.6 Maintaining E-Mail Address for Business Partner and SU01 User..................53

4.2 Setting Up the Display of Invoices..........................................................................53

4.3 Setting Up Shipping Status Tracking......................................................................54

4.3.1 Preparing Tables..............................................................................................54

4.3.2 Creating a Vendor............................................................................................55



4.3.3 Creating an Express Delivery Company...........................................................56

4.3.4 Changing an Existing Delivery.........................................................................58

4.3.5 Creating a Test Entry.......................................................................................59

5 Appendix....................................................................................................................... 60

5.1 Administration of Language and Country Settings..................................................60

5.2 SAP E-Commerce Administration Console.............................................................60

5.2.1 Application Cache Statistics.............................................................................61

5.2.2 Catalog Cache Statistics..................................................................................62

5.2.3 Application System Cache Statistics................................................................63

5.2.4 Java Connector Pools......................................................................................63

5.2.5 Java Connection Sharing.................................................................................64

5.2.6 CCMS Heartbeat Customizing.........................................................................64

5.2.7 Lean Basket Data Migration to NetWeaver 04.................................................64

5.2.8 Scheduler Administration.................................................................................64

5.2.9 Logging............................................................................................................64

5.2.10 Version.............................................................................................................65

5.3 Modifying and Enhancement of the SAP E-Commerce Web Application Framework..............................................................................................................65

5.4 Restarting single Java Applications using the Visual Administrator........................65

5.5 Additional Installation Information on SAP E-Commerce for SAP ERP.................66



SAP E-Commerce with SAP ERP (220) Configuration Guide

1 PurposeThe building block SAP E-Commerce with SAP 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 PreparationSAP E-Commerce for SAP 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 ERP, SAP WAS Java as well as the Java Web Components included in SAP ERP 2005.

Optionally, you can use Internet Pricing and Configurator, TREX as Catalog and Search engine and Web Server for document publication.

2.1 PrerequisitesThe system landscape including all SAP ERP 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 854170. How to configure your SAP Virtual Machine Container (VMC) is described in the configuration guide IPC in SAP E-Commerce for SAP ERP in http://service.sap.com/erp-inst SAP ERP SAP ERP 6.0 Installation.

TREX Installation: you have installed and configured your TREX Engine as described in the installation guide Installation - Search and Classification TREX Single Host in http://service.sap.com/instguidesnw70 Installation Installation - Standalone Engines.

Web Server: MS Internet Service Manager as web server is described in this configuration guide.

2.1.1 SAP NotesBefore 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 with SAP 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 ).


http://service.sap.com/notes

http://service.sap.com/instguidesnw70%20

http://service.sap.com/erp-inst


SAP Notes that are relevant for SAP E-Commerce with SAP 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

854170 Activating the component "VM Container 70

837119 ISA 5.0: Catalog replication (CONSULTING!) 5.0

128947 Correction of SD document indexes with RVV05IVB 6.0

411653 Billing documents are not displayed in the web shop 4.0

1083667 During logon an FileNotFoundException occurred 5.0

3 Basic Configuration

3.1 Product Catalog

3.1.1 General Information about the Product CatalogThe Internet product catalog is based on the data from the Product Catalog component in the ERP system.

The product catalog contains the whole range of products that can be sold in SAP Internet Sales Web shop. In addition, it contains certain shop-relevant data such as the language and currency. Maintaining or administering the product catalog is, therefore, a core activity for the vendor.

3.1.2 Creating Product Catalog

3.1.2.1 Defining the Basic Data

Please check the Delta Guide.

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

Procedure1. 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_CAT Product catalog Best Practices

Catalog type blank

3. Choose Basic Data and make the following entries.

Setting Value Description

Baseline DE

Auth.group blank Specify, if you want to manage access authorizations

Un of 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 SAP ERP.

Key Date blank Key date on which the prices for the product catalog are determined.

Reference Cust. <Enter value> The Reference Customer is also used for the Pricing Procedure when list prices (Catalog Pricing) are used.

Sales Organization <Enter value> Specify the Sales Organization your catalog belong to

Distr. Channel <Enter value> Specify the Distribution Channel your catalog belong to

Division <Enter value> Specify the Division your catalog belong to

Display Currency <Enter value> Specify the Display Currency your Web shops should use

Display pricesselect Indicator for displaying prices in product

catalog maintenance

4. For the Web Shop Management in SAP E-Commerce for SAP ERP it is important to create at least one Catalog Variant. Therefore create a variant for your catalog.


Variant <Enter value> Enter a unique ID for your Variant

Language <Enter value> Specify the language for your Variant

Currency <Enter value> Specify the currency for your Variant

5. For a Web Shop in a second language create a second variant and maintain later all material descriptions in the second language..


Variant <Enter value> Enter a unique ID for your variant

Language <Enter value> Specify the language for your variant

Currency <Enter value> 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.

6. Choose Save.

3.1.2.2 Creating Layout Areas




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. Make sure that your catalog name is entered

Setting Value (Example)

Description

Catalog BP_CAT Enter the name of your catalog

3. Choose Layout.

4. Select the word Layout and choose the Create layout area icon in the application toolbar.

5. Define a name for the new Layout area.

6. Add your products to the new Layout area (for further information, see below).

7. Specify if you want to manage access authorizations for the layout area.

8. Choose Save.

If a layout area 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

UseYou 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.







Setting Value (Example)

Description


3. Choose Layout.

4. Select a layout area.

5. Select a material, and choose Texts in the application toolbar, or double-click the T checkbox in the material row.

6. You can maintain the text here or copy it from the material master data.

7. Choose Edit Copy Material Text in the application toolbar.

8. Select the text type you want to copy, for example, Sales and Distribution text.

9. Choose Copy.

10. Choose Back.

11. Choose Save.

3.1.3 Document Publication

3.1.3.1 Creating the Directory for Document Publication

UseThe documents for the product catalog are stored in a separate directory, which must be accessible by HTTP.

Therefore, you can create a new directory <YOUR_DIRECTORY>, which has to be a subdirectory of your HTTP root directory. In case the directory catalog already exists, you can use this directory.

ProcedureWeb 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 of The MS Internet Service Manager. 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 tab Home Directory 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.

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.

9. Select the option Share this folder, and enter the alias catalog in the field share name.

3.1.3.2 Maintaining Properties of the Default Web Site

UseAfter 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.

ProcedureWeb 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.

3. Ensure that under Access Permissions the Read, Write and Directory browsing fields are selected.

3.1.3.3 Setting of TCP Port

UseBecause of security settings, it may be necessary to change default http port. Usage of default http port 80 could be blocked within your network.

ProcedureWeb Server Maintaining TCP port of the Default Web Site

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

2. Choose the Web Site tab.

3. Ensure that under Access Permissions the Read, Write and Directory browsing fields are selected. Change the TCP Port, for example <portnumber>.



3.1.3.4 Copying Pictures to Folder on the Web Server


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

3.1.4 Document ManagementThrough 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


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

ProcedureFor 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, <document number>.

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, <name.jpg> or <name.gif>.

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, <name.jpg> or <name.gif>.

14. Choose Enter.

15. Confirm the information dialog box.

16. Choose Save.

3.1.5 Assigning Documents to Product Catalog

UseYou 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.





Setting Value (Example) Description


3. Choose Layout.

4. Select a Layout Area.

5. Select a Material.

6. Double-click the D checkbox.

7. Enter L01 as type and the requested document number as document.

8. Choose Enter.

9. Choose Documents, if you want to assign a picture on layout area level.

10. Enter L01 as type and the requested document number as document.

11. Choose Enter.

12. 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:

http://service.sap.com/instguidesnw70 Installation Installation - Standalone Engines

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 http://service.sap.com/instguidesnw70

3.1.6.2 Creating the Search Server Relation (optional)

UseBefore 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, 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.

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 Search Engine Setting, choose Connection Test.

15. Sometimes you have to restart the transaction SRMO before the connection test works.

ResultA 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)

UseYou 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.

Procedure1. 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 ERP server to a TREX server. The following parameters can be set when replicating a catalog:

Parameter Value Remarks

Catalog ID* BP_CAT 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



Parameter Value Remarks

option which is also the default setting. If, however, you experience performance problems or memory problems, see SAP Note 837119 for further information.

Departure country for tax det.

DE

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.

Read images checked Activate this flag only if you have maintained images in the product catalog and you want to see them in the ECO web shop

Read prices Activate this flag only if you have maintained prices in the product catalog and you want to see them as list prices in the ECO web shop.

Read configurability flags

Not checked Activate this flag only if you configurable products and/or product variants in the product catalog and you want to use IPC with the ECO web shop

Support IPC Pricing checked Activate this flag only if you use IPC 5.0 for pricing (e.g. customer-specific prices). Otherwise deactivate this flag to improve replication performance.

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.1.6.4 Specifying the Address of the TREX Name Server

UseBefore you can use your catalog replicated to the TREX in the web shop, you have to specify the address of the TREX Name server in the SAP NetWeaver Visual Administrator of J2EE Engine. The TREX Java client needs to know the address of the TREX name server in order to communicate with the TREX servers.

ProcedurePlease refer to the installation guide SAP NetWeaver 2004s Standalone Engine Search and Classification (TREX) Single Host from http://service.sap.com/instguidesnw70 , chapter Specifying the Address of the TREX Name Server.

3.2 XCM Configuration for B2B and B2C

UseSince Version 4.0 of SAP E-Commerce for SAP 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 SAP ERP.

3.2.1 Assigning J2EE Admin Role to User Profile

UseBefore 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 ERP user and password.


Transaction code SU01

SAP menu Tools Administration User Maintenance Users

2. Enter your User and choose Change.

3. Choose the Roles tab.

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

UseInternet 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 menu Tools Administration 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.

6. Double-click the single role. Perform the following steps for each single role assigned to the collective role.

7. Choose the tab Authorizations.

8. Check if the Authorizations tab 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

UseXCM 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

UseCheck 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: <YOUR_CONFIGURATION>

B2C: <YOUR_CONFIGURATION>


Web browser XCM

B2B URL http://<host>:<port>/b2b/admin/xcm/init.do

B2C URL http://<host>:<port>/b2c/admin/xcm/init.do

Username <Your User>

Password <Your 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 =<yourscenario> (the name of configuration is case-sensitive).

5. Choose Create.

6. Choose Save configuration.

7. Choose Display to switch to display mode.

If you are planning to use the TREX search engine for storing your ERP product catalog, choose r3standardpitrex as pre-configured SAP Configuration.



3.2.5 Configuring the ERP Connectivity

UseThe 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

UseIn 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.




2. In the User field, enter WEBLOGIN.

3. Choose Create (F8).

4. Make the following entries:

Address tab

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

User type Service

Password welcome

Profile tab

Profiles SAP_ALL and SAP_NEW

Roles tab

Role SAP_ISA_UADM_RFC



5. Choose Save.

3.2.5.2 Creating the JCO Component

UseYou 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





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, <YOUR_JCO_COMPONENT>), and choose Create.

5. Choose Base Configuration, for example server_connect used for direct connection to SAP Server.

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

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

passwdPassword for SAP system. This password is encrypted when it is stored. (for example, welcome)

user User name (for example, WEBLOGIN)



maxcon Maximum size of SAP Java Connector connection pool.

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


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)

UseOptionally, 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





2. Access the ShopComponent:

XCM Menu Start Components Customer Shop

3. Choose Edit to switch to edit mode.

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

5. Make the following entries.

Name Value Description

Base Configuration r3shop_b2b for B2BShop scenario is Business to Business (B2B) and backend system is ERP.

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-PathFor 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 otherwise leave it blank.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.

defaultShopIdShop Id for default shop for B2B, B2C and CCMS Heartbeat



3.2.7 IPC Component

UseAs 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 Price Determination please use Document IPC in SAP E-Commerce for SAP ERP from http://service.sap.com/erp-inst SAP ERP ERP 6.0 Installation.

3.2.8 Creating the Web Catalog Component

UseThis 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





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, <YOUR_CAT_COMPONENT >), and choose Create.



imageserver

The directory you have created above.

For example: http://<host>:<port>/<directory_name>/

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 10The 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




priceDecimalPlace false

Parameter to display or hide decimal places for Prices in the WebCatalog



ResultAfterwards, you can access your new component as a subnode of Web catalog:XCM Menu Start Components Customer webcatalog <YOUR_CAT_COMPONENT>

3.2.9 Creating UI Component

UseIn this step you configure the behavior of the user interface of the web application.


Web browser UI Component Configuration





2. Access the UI component.

XCM Menu Start Components Customer ui

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



language: ENDefault Language for User interface and Backend communication

enable.priceAnalysis: trueShow or hide pricing conditions display

configOnlineEvaluate:true Turn on IPC

configuration online evaluation

enablerelogincookie.core:

true If enabled, a temporary cookie will store all relevant login parameter for a relogin.




enable.nonCatalogProducts:

true Activates or deactivates the ordering of products which are not in the catalog.

showstacktrace.isacore:true If set to 'true' a

stacktrace is shown if an application error occurs.

showmodulename.core:

false If set to 'true' the name of the JSP is shown when the JSP is displayed.

exact.search.isacore:true perform an exact or non-

exact search in the product-list tab

maxhits.search.isacore:${maxhits.search.isacore.isa.sap.com}

Determines the maximal number of hits for the product-search

maxhits.search.action.businesspartner:

${maxhits.search.action.businesspartner.isa.sap.com}

Determines the maximal number of hits for the customer-search

theme.core: <leave empty>

Enable you to manage different records of Mime objects (e.g. picutures, stylesheets). The parameter specified here determines which record is to be used.

mimes.core: <leave empty>

URL to mimes (e.g. pictures, stylesheets etc.) if placed on an external web server.

enable.orderdownload: true

Activates or deactivates the order download functionality. This parameter should only be used in HOM configurations.

enable.pers: trueEnable personalization for the application configuration.

ui.fields.order.deliveryPriority: editableVisibility and availability of the field delivery priority

ui.fields.order.shippingCondition: editableVisibility and availability of the field shipping condition




ui.fields.order.bomExplosion: hiddenEnable display of bill of materials (BOM explosion)

ui.fields.order.subitemDetailView: hiddenControls the enabling of the sub items detail view



ResultAfterwards, you can access your new ui configuration as a subnode of ui:XCM Menu Start Components Customer ui < myUIData >

3.2.10 Assigning the Components to the Configuration

UseAll 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





2. Access your customer-specific configuration:

XCM Menu Start Application Configurations Customer <YOUR_CONFIGURATION>

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

Jco data <YOUR_JCO_COMPONENT> JCO

Ipcjco data <YOUR_JCO_COMPONENT> JCO

Ipc data ipcdefault IPC




Shop data

B2B: r3shop_b2b or <YOUR_SHOP_COMPONENT>

B2C: r3shop_b2c or <YOUR_SHOP_COMPONENT>

SHOP

Ui data < myUIData> UI

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

Webcat data <YOUR_WEBCAT_COMPONENT> 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.

9. C hoose Display to switch to display mode.

3.2.11 Maintaining General Application Settings

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


Web browser XCM





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. Choose Display.

7. After you performed all XCM Settings, restart your application.

8. To restart, access the activity using the following navigation option:

Web browser SAP NetWeaver Administrator

B2B URL http://<host>:<port>/nwa

SAP NetWeaver Administrator Menu

System Management Administration Applications

9. Search for your application (for example, B2B or B2C).

10. Select your application in the Application List.

11. Stop and start your application – use the application detail Status tab.

3.3 User ManagementUsers 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 ManagementIn 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



Usertype B2B B2C Shopadmin

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.

UseThis 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.

Procedure

1. Access the activity using the following navigation option:


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

UseBefore 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://<host>:<port>/isauseradm/admin/xcm/init.do



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, <yourscenario> (the name of configuration is case- sensitive).

5. Choose Create.

6. Set your configuration as default configuration.

7. Set the checkbox Active Configuration.

8. 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






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, <YOUR_JCO_CONFIGURATION>), and choose Create.

4. Choose your base configuration, for example server_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.


9. 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

UseYou have to define specific parameters for web application regardless if you are using SSL or not.


Web browser Maintaining General Application Settings





XCM Menu Start General Application Settings Customer isauseradm isauseradmconfig

3. Choose Edit.


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://<host>:<port>/nwa



8. Search for your application (for example, isauseradm).


10. Stop and start your application by using the application detail Status tab.

3.3.3.4 Creating the User for User Admin Shop Manager

UseIn 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.



Procedure1. Access the activity using the following navigation options:



2. In the User field, enter USERADMIN.


4. Enter the following data:

Address tab

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

Alias USERADMIN

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

Role SAP_ISA_UADM_MANAGER

5. Choose Save.

3.3.3.5 Creating SU01 Internet User for the Customer


For the SAP Best Practices scenario, use this method to create an internet user.

UseThis 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.




Web browser

Creating an SU01 Internet User for the Customer

URL http://<host>:<port>/isauseradm/useradmin/init.do?scenario.xcm=<yourscenario>

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.

ResultYou 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

UseIn 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.


Web browser

Creating a Super User for the Customer

URL http://<host>:<port>/isauseradm/useradmin/init.do?scenario.xcm=<yourscenario>

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

3. Choose Create New User.



4. Choose Create New User And New Contact Person.

5. 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

6. Enter the Company ID and select refresh button.

7. Assign the authorization, select Full B2B Authorizations and Super User for User Management, and choose the > button.

8. Choose Continue.

9. Enter the communication data: language, telephone, fax.

10. Choose Create.

ResultYou 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

UseIn 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.




2. In the User field, enter B2CREFUSER.



Address tab

Last Name B2C Reference User

Logon data tab

User type Service


Roles tab

Role SAP_ISA_B2C_RFC

Role SAP_ISA_B2C_FULL

5. Choose Save.



3.4.2 Identifying Relevant ERP Account Groups (SAP ERP)

UseIn this activity, you identify an account group with internal number assignment. The reference business partner must be created within this account group.


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 YB03 to create your reference customer.

3.4.3 Creating ERP Reference Customer (SAP ERP)


For the SAP Best Practices scenario, use this method to create an ERP Reference Customer.

UseYou 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.


Transaction code XD01

SAP menu Logistics Logistics Execution Master Data Partner Customer Create Total

2. Choose Customer Create: Initial screen. Enter Account group, Company code, Sales Org., Distribution Channel, Division.



3. Choose Enter.

4. Choose the Create Customer: General Data Address tab.

5. Enter Title, Name, Search term1, Street, house number, Postal Code, City, Country, Region, Time Zone, Transportation Zone, Telephone, Fax.

6. Choose the Company Code Data button.

7. Choose the Create customer: Company code data: Account management tab.

8. Enter the Recon. Account, Sort key, cash mgmt group.

9. Choose Create customer: Company code data: Payment transactions tab.

10. Enter Terms of Payment and Bank statement.

11. Choose the Create customer: Company code data: Correspondence tab.

12. Enter Dunn. Procedure

13. Choose the Sales Area Data button.

14. Choose the Create customer: Sales Area Data: Sales tab.

15. Enter Customer group, Currency, Cust. Price proc., Cust. Stats grp.

16. Choose the Create customer: Sales Area Data: Shipping tab.

17. Enter Delivery priority, Shipping conditions, Delivery Plant.

18. Choose the Create customer: Sales Area Data: Billing document tab.

19. Enter Inco terms, Terms of payment, Account assignment group, Tax classification.

20. Choose Save.

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

3.5 Web Shop Management

3.5.1 XCM Configuration for the Shopadmin Application

UseWeb 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

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


Web browser Creating a Customer-Specific Configuration

URL http://<host>:<port>/shopadmin/admin/xcm/init.do




XCM Menu Start Application Configurations SAP r3shop

3. Select the default configuration for r3shop, and choose Edit.

4. Enter a name <YOUR_CONFIGURATION> for the new configuration in the input field.

5. Choose Create.

6. Maintain Description and mark this configuration as default configuration and active configuration.



ResultThe new configuration has been created and can be accessed via:

XCM-Menu Start Application Configurations Customer <YOUR_CONFIGURATION>

3.5.3 Creating the JCO Component

UseNext, 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.








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, <YOUR_JCO_CONFIGURATION>) and choose Create.

4. Select Base Configuration, for example server_connect used for direct connection to SAP Server.


5. 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.



8. 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.

ResultAfterwards, your can access your new component as a subnode of JCO:XCM-Menu Start Components Customer JCO <YOUR_JCO_COMPONENT>

3.5.4 Creating the Shop Component (optional)

UseOptionally, you can configure here additional settings used by the selected shop type.




Web browser Creating the Shop Component




2. Access the shop component:

XCM Menu Start Components Customer Shop

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

4. Make the following entries.


Object-PathFor 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

UseAll 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.

Procedure1. Access your customer-specific configuration:

XCM Menu Start Application Configurations Customer <YOUR_CONFIGURATION>

2. Choose Display advanced settings.

3. Check or make the following entries. Leave the other entries as they are.


jcodata <YOUR_JCO_COMPONENT> JCO



shopdata <YOUR_SHOP_COMPONENT> SHOP

Usertype R3_SU01_User

4. Select 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

UseThe first step is to define parameters specific to the shopadmin application.


Web browser





XCM Menu Start General Application Settings Customer shopadmin shopadminconfig

3. Choose Edit.


5. Choose Save.

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



7. Search for your application (for example, shopadmin)


9. Stop and start your application by using the application detail Status tab.

3.5.7 Creating the User for Web Shop Manager

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






2. In the User field, enter WEBADMIN.



Address tab

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

Alias WEBADMIN

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

User type Dialog


Roles tab

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


UseThe 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 with SAP 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.

ProcedureWeb browser

Shopadmin

URL http://<host>:<port>/shopadmin/shopadmin/init.do?language=<language>

<host>:<port>: host and port

<language>: Logon language, for example en or de

1. Log on to Web Shop Management using WEBADMIN user.

2. Choose Create New Shop for specific scenario, for example B2B/B2C.

3. You can edit the following entries:

Field Value Description

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

Description <Enter value> Enter a description for the Web Shop.

General Information tab

General Settings

Language <Enter value> Enter the language for the shop in ISO code. You can only view those shops with the same language as the logon language.

Country <Enter value> 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 <Enter value> 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 <Enter value> Enter the ERP country group. This is a list of countries that are permissible for a shop.

Address Format <Enter value> 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 <checked> 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 chapter Creating B2C Reference User.

Relevant for B2C when an SU01 user scenario is active. During the registration process, newly created users will be created with the reference user and later get their authorizations from there.

Business Scenario B2B/B2C Type of scenario for which the web shop is to be used. You can choose either B2C or B2B, or both.

Catalog tab

Product Catalog

Currency <Enter value> 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_CAT 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

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 web application.



R/3 Order Type <Enter value> Enter the ERP transaction type for orders generated from the 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 <Enter value> Enter the sales organization for orders

Distribution Channel <Enter value> Enter the distribution channel for orders

Division <Enter value> 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 reference customer creation see please chapter Creating ERP Reference Customer (SAP ERP)

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 reference customer creation see please chapter Creating ERP Reference Customer (SAP ERP)

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 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

Not 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.

Prerequisite: ERP customizing for credit card processing must be available.

Payments: Preassignment: Payment

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

Customers tab

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.

For each additional language a new Web Shop has to be created.

3.6 Request for Quotation Settings

3.6.1 Changing Order Type for Request for Quotation

UseIn this activity, you identify the order type for your quotation and change the proposed pricing date. Enter today’s date in this field.


Transaction code VOV8

IMG menu Sales and Distribution Sales Sales Documents Sales Document Header Define Sales Document Types

2. Select Sales Document Type IN and choose Details.

3. In the Requested delivery date/pricing date/purchase order date tab select for the Prop. f. Pricing Date - blank (proposal based on today’s date).

4. Choose Save.



4 Additional Configuration

UseThe Best Practices Configuration Guide contains the information necessary to set up the Business Scenario with SAP E-Commerce for SAP 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 SAP ERP.

4.1 Setting Order Confirmations via E-MailIn common e-commerce environments, it is possible to send an order confirmation via e-mail. This is the case in SAP E-Commerce for SAP ERP. Here, the SAP ERP 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 5.0 for SAP ERP Bus. Scenario Config Guide 5.0 in service.sap.com/erp-inst SAP ERP ERP 6.0 Installation

4.1.1 Maintaining Output Types

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


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, enter the access sequence 0004 (SalesOrg/Sales Order Type).

5. On the Default values tab, set transmission Medium 5 External send.

6. Choose Enter.

7. Choose only copy entry in the upcoming dialog box, Specify object to be copied.

8. Select YBAI.

9. Choose Processing routines.

10. Choose New Entries.




Output Type

Application Transport-Medium

Program FORM Routine

PDF/Smartform

YBAI V1 5 External send

/SMBA0/AA_RVADOR01 ENTRY /SMBA0/AA_SDORC

12. Choose Partner Functions


Medium Function Name

5 SP Sold-to party

14. Choose Save.

4.1.2 Maintaining Output Determination Procedure

UseThe 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.


Step Cntr Ctyp Requiremnt

Next available 1 YBAI 2

6. Choose Save.

4.1.3 Creating Output Condition Records

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

Procedure


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 for your sales organization (for example 1000).

Sales Doc Type

Name Funct Medium Date/Time Language

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 Selected

Release after output Selected

SAP Cover Page Do Not Print

Cover Page Text Order Confirmation

7. Choose Save.

4.1.4 Allocating Sales Document Header

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

Procedure


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

UseSAPconnect 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 host, that is analogous to mail.sap.corp>

Mail Port 25

Code Page 4110 Unicode UTF-8

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, <sysid>.<corporate>.com, and continue.

Ask your system administrator for the right domain.



4.1.6 Maintaining E-Mail Address for Business Partner and SU01 User

UseThe 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.

3. Be sure to be in change mode (choose Switch Between Display and Change)

4. On the Address tab, enter the e-mail address.

Field Name Field Entry

Communication

E-Mail <mail address>

Standard Comm.Mtd E-Mail

5. Choose Save.

6. Access the activity using the following navigation option:


7. Check if E-Mail address is maintained for your SU01 user created in chapter Creating SU01 Internet User for the Customer, otherwise maintain E-mail address and Standard Comm.Mtd. for user.

4.2 Setting Up the Display of Invoices

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

PrerequisitesYou have installed SAP E-Commerce for SAP ERP.


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 transaction SE38.

5. Start the report RVV05IVB to restructure the partner index for existing bills.

6. On the selection screen, in the section Billing Documents, choose the checkbox Partner Index. Please note that the restructuring can take some time and should therefore be started as a background job. For further information, see report RVV05IVB in SAP Note 128947.

The partner index is automatically written when new bills are created.

4.3 Setting Up Shipping Status Tracking

UseSAP E-Commerce for SAP ERP enables Web shop customers to track the shipping status of the products they have ordered. If a shipping agency offers shipping information on the Internet, customers can access the shipping status directly via a hyperlink. This enables customers to track their delivery during the shipping process.

PrerequisitesURL http://help.sap.com

SAP ERP Documentation

SAP ERP ERP Central Component Logistics Sales and Distribution (SD) Shipping (LE-SHP) Goods Issue Including Express Delivery Company Requirements

If you work with express delivery companies, read the documentation in the SAP library.

The shipping agency offers the shipping status tracking service.

The shipping agency has assigned a bill of lading for the order and sent it to the Web shop operator.

You have created a forwarding agent partner function in transaction VOPA in the SAP system and assigned it to the delivery note LF (for delivery category LF).

4.3.1 Preparing Tables


Transaction code SM30

SAP menu System Services Table Maintenance Extended Table Maintenance


http://help.sap.com/


2. Call table TCAURL. Enter the required data.

Example

Category User ID

URL

TRACK_URL DHL http://www.dhl.com/track/track.post-track?awb=<AWBN>&origin=<COUNTRY>

TRACK_URL FEDEX http://www.fedex.com/cgi-bin/track_it?trk_num=<AWBN>&dest_cntry=<DES_CTRY>&ship_date=<SHIPDATE>

TRACK_URL UPS http://www.ups.com/tracking/tracking.cgi?tracknum=<AWBN>

3. Call table TCAVAR. Enter the required data.

Example

Category User ID Function Module

URL <AWBN> WS_READ_AIRWAYBILLNUMBER

URL <COUNTRY> WS_READ_COUNTRY_OF_ORIGIN

URL <DES_CTRY> WS_READ_DEST_COUNTRY

URL <SHIPDATE> WS_READ_SHIPDATE

4.3.2 Creating a Vendor


Transaction code XK01

SAP menu Logistics Materials Management Purchasing Master Data Vendor Central Create

2. A vendor for the shipping agency has to be created, for example, UPS:

Enter UPS as Vendor ID.

The name of the forwarding agent (field Vendor) must be identical to the user ID in table TCAURL.

Enter your actual company code.

Enter your actual Purchasing Organization.

Enter 0002 as account group.

Press ENTER to access the Create Vendor: Address screen.

Enter all mandatory data and save your entry.



4.3.3 Creating an Express Delivery Company

ProcedureTransaction code VTRC

SAP menu Logistics Logistics Execution Master Data Partner Service Agent Maintain Express Delivery Company

A corresponding express delivery company has to be created and assigned to the vendor.

1. Choose Create, and create a new express delivery company.

2. Enter UPS as express delivery company, and 22222W as the account number with express delivery company (Account w/Exp.DlvCo).

3. Press ENTER to create the express delivery company.

4. Choose Goto Assign Service Agent to Express Delivery Company.

5. Create two new entries with the value UPS as the number of the forwarding agent and the express delivery company:

Number of forwarding agent (ServcAgent)

Export indicator (ExpID)

Express Delivery Company (Exp.DlvCo)

UPS UPS

UPS X UPS

6. Return to the main screen.

7. Choose Goto Express Delivery Company Control. Maintain this screen as follows:

Active activated

Set Tracking Status manually activated

Tracking Data available in Days 100

Max Nr. Parcels Multi-Track 5

8. Maintain the Data Provider screen:

URL for Business Connector http://saptools.ups.com/servlet/XsiBapiConfig

9. Save your entries

10. Choose Goto Express Delivery Company and Meta Data.

11. If no entry exists, create a new entry with the following values:

Express Delivery Company UPS

Active activated




12. Make sure that your shipping points are assigned to the express delivery company by choosing Shipping point: active.

13. If there are no shipping points, please add your shipping points by choosing New entries.



14. Choose Meta Data, and create the following new entries:

Express Delivery Company

UPS UPS UPS UPS

Express Delivery Company's Data Field

ROUTECODE SERVICELEV SHIPACCT TRACKN

Description Route Code Service Level Carrier number Tracking number

Active activated activated

Data Field Length

2 2 5

Qualifier ROUTECODE XSISRVC SHIPACCT TRACKN

Document Cat X J J X

Higher Doc Cat J J J

Default Value 03 22222W

Function Module

XSI_GET_CARRIER_ROUTING

XSI_GET_SERVICE_CD_ROUTE


16. Choose Goto Express Delivery Company Master Data.

17. If no entry exists, create a new entry with the following values:

Express Delivery Company UPS

Active activated




18. Click on Service Code and add at least one new entry:

Exp. Del. Comp. Service Service Code

Service Group

XSI: Carrier´s Service Description

UPS 03 BLACK SQUA

GND UPS Ground

19. Click on URLs, and create the following entries:

Carrier XSI URL TYP / Significance URL

UPS Service Code Documentation

http://www.ups.com/sap/interface/servicecodes.html

UPS Logo http://www.ups.com/sap/interface/servicecodes.html

UPS XML Server http://saptools.ups.com/servlet/XsiBapiConfig

UPS Express Delivery Company http://www.ups.com

UPS Individual Parcel Tracking http://wwwapps.ups.com/etracking/tracking.cgi?&TypeOfInquiryNumber=T&HTMLVersion=4.0&sort_by=status&InquiryNumber1=<TRACKN>



Carrier XSI URL TYP / Significance URL

UPS Multiple Parcel Tracking http://wwwapps.ups.com/etracking/tracking.cgi?&TypeOfInquiryNumber=T&HTMLVersion=4.0&sort_by=status{&InquiryNumber#=<TRACKN>}

20. Click on Tracking Status, and add the new entries:

Service Agent (Srvc Agent)

Track Details (TrckDetail)

Track Status (TrckStatus)

Status

UPS D Partially Picked up

C

UPS E Delivered D

UPS I No tracking data A

UPS M No tracking data A

UPS P No tracking data A


22. On the Number range tab, make the following entries:

Object Name TRACKS

Number Range Number 02

Number Of Subobjects UPS

Starting Point 1000

End 9999

23. Choose Set Number Range Immediately.

24. Choose Save.

4.3.4 Changing an Existing Delivery


Transaction code VL02N

SAP menu Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Change

You have set up shipping status tracking.

As the Web shop operator, you must perform the following tasks:

2. Select an existing delivery.

3. Select Go to Header Partners. Enter the data of the corresponding forwarding agent.

4. Select the Shipment tab. Enter the transportation route and bill of lading under BillOfLad.



4.3.5 Creating a Test Entry


Transaction code SE16

SAP menu Tools ABAP Workbench Overview Data Browser

For test purposes, you can create a demo entry manually in transaction SE16.

2. Enter the table VTRKH and choose Create.


Value Description

VBTYP J Delivery

VBLEN 80000XXX Bill Of Delivery

XSITD UPS Express Delivery Company

UEVBTYP J Delivery

UEVBELN 80000XXX Bill Of Delivery

TRACKN 9999999999999999 Bill Of Lading

SHIPACCT 22222W Account of Expr.Del.Comp.

ROUTECODE 000001 Route

ROUTELDAT 17.08.2007 Date of Delivery

XSISRVC 03 Servicetyp

The service type 03 must have already been created in the section Creating an Express Delivery Company, step 18 (Create new entry for Service Code).

After this entry, the Web shop should be able to display an icon of a driving truck and link it to the Web site of the corresponding express delivery company.



5 AppendixThe Best Practices Configuration Guide contains the information that is necessary to set up the business scenario with SAP E-Commerce for SAP ERP. It cannot describe all the features SAP E-Commerce for SAP ERP offers. Therefore, an appendix is added to the Best Practices Configuration Guide for SAP E-Commerce for SAP ERP, which contains more information about the configuration SAP E-Commerce for SAP ERP.

5.1 Administration of Language and Country Settings

ProcedureWeb browser XCM





Language Settings

The language used within a configuration can be set as follows:

Externally using the parameter language. (add ?language=XY to your web shop URL)

In the XCM Component Configuration ui, which controls the user interface of the web application.

In the XCM Component Configuration jco, which controls the connection parameters to the ERP system.

The language setting in the component jco can be overwritten by the request parameter language in the calling URL, or by the value set in the XCM component ui.

Only those shops which correspond to the language you have set are displayed in the shop list.

Country Settings

The country of the Web shop you selected in shopadmin application is used. The correct currency and date format will be derived from the country and language.

5.2 SAP E-Commerce Administration Console

ProcedureWeb browser SAP E-Commerce Administration Console

B2B URL http://<host>:<port>/b2b/admin

B2C URL http://<host>:<port>/b2c/admin





The following links are available:

Extended Configuration Management (XCM) Administration

Application Cache Statistics

Catalog Cache Statistics

Application System Cache Statistics

Java Connector Pools

Java Connection Sharing

CCMS Heartbeat Customizing

Lean Basket Data Migration to NetWeaver 04

Scheduler Administration

Logging

Version

5.2.1 Application Cache Statistics On this page, you can observe the caches that are currently being used by the application and their size and utilization.

The table columns have the following meaning:

Name Here you can find the internal name of the cache. This name uniquely identifies a cache within the application and cannot be changed by the administrator.

Status Actual status

max. size Specifies the maximum number of objects that the cache can hold. This number cannot be changed in the existing version by the administrator, and is set to a suitable size.

actual size Specifies how many objects the cache currently holds.

Hits Describes the number of successful read attempts from the cache. This numerator is increased by one each time an object is removed from the cache without necessitating a read from the backend.

Misses Number of unsuccessful read attempts from the cache. This numerator is increased by one each time a requested object is not available in the cache and has to be read from the backend.

You can reset the contents of the cache using the link clear that is in the last column. This always makes sense if you have changed data in the backend and for that reason the old data should be removed from the cache.



The following caches are currently created by the application:

ShippingConditions Possible terms of delivery that are available (offered as a drop-down box). If the Web shop customer does not specify a specific term of delivery, the term of delivery of the sold-to party is determined from ERP and is transferred to the purchase order.

CardType The possible credit card categories (VISA, American Express, and so on).

Shoplist This cache saves the list of the available Web shops of the back-end system. Delete this cache if you have added a new Web shop.

BoBestsellerCache This cache saves the list of current product recommendations of the system (bestsellers, for example). Delete this cache if you have made changes to the bestseller list and if you have replicated the data.

5.2.2 Catalog Cache StatisticsOn this page, you can check the parameters of the cache that is created for the catalogs.

The following times are displayed on the top half of the page:

Configured expiration time

Time interval that was defined for the parameter expiration during the initialization of the catalog cache.

Configured removal time

Time interval that was defined for the parameter removal during the initialization of the catalog cache. This specification does not have to be made if no timeframe was specified there.

Next check of remaining life time

Time that specifies when the thread that removes the catalogs whose life cycle is less than or equal to zero should be restarted. The thread is started hourly.

Information about the individually buffered catalogs is displayed in the table on the lower half of the page.

The table columns have the following meaning:

Key Key under which the catalog is managed in the cache.

Catalog Guid Unique indicator of the catalog (name, variant).

Time Stamp Time stamp that specifies when the catalog was last accessed.

Remaining life time Time specification that shows when the catalog was removed from the cache, if it was not accessed again in the meantime. The check of this time takes place hourly. It is therefore possible that the time specification can be negative.

You can explicitly remove a catalog from the cache using the link Remove that is in the last column.



5.2.3 Application System Cache StatisticsThis page gives you an overview of system caches.

The table columns have the following meanings:

Cache Name Here you find the internal name of the cache. This name identifies a cache within the application.

Num Objects Specifies how many objects are currently stored in the cache.

Hits Describes the number of successful read attempts from the cache.

Time To Live [min]

Time in minutes that an object is stored in the cache until it is removed from the cache, if this object is not accessed during this time.

Description Description of the cache.

Clear A hyperlink which is used to delete the cache.

The following caches are currently available:

XCM_APP_SCOPE Stores configuration files with application scope

XCM_SESSION_SCOPE Stores configuration information used by the Extended Configuration Management

r3matnrconv Used for caching some material number conversion results. Only relevant when running ECO ERP

r3cust Used to temporarily save the customizing that is read from the ERP back-end system. Only relevant when running ECO ERP.

r3formatters Used to temporarily save the locale and currency-dependent formatting for the date and currency conversion. Only relevant for ECO ERP.

MaintenanceObject-Cache

JCO Used to temporarily save calls from the SAP Java Connector to the SAP system.

5.2.4 Java Connector PoolsThe page gives information about Connector Management to the SAP system, which takes place via the SAP Java Connector.

The page is divided into the following areas:

Java Connector (JRFC)

Version of the SAP Java Connector.

JCo Pool Statistics

The following table gives information about the Java connection pools that are available on the application server:

pool name Name of the connection pool

max pool size The maximum size of SAP Java Connector connection pool

max cons used The maximum number of connections to the SAP system that are required per pool up to that point in time

num current used cons The number of connections that are currently available in the pool



The page displays all of the SAP Java connector pools that are available on the application server, and not just the pools of the Web application in which the administration page is.

5.2.5 Java Connection Sharing

UseThe connection handling mechanism in the J2EE Engine enables the sharing of a single physical connection between multiple users – that is, it supports multiple connection handles associated to a single physical connection. This feature is implemented for optimization purposes and is especially useful when the back-end system allows for establishing a limited number of connections.

5.2.6 CCMS Heartbeat Customizing

UseSAP E-Commerce for SAP ERP is integrated with the Computing Center Management System (CCMS) allowing a system administrator to monitor information concerning several applications, including B2B or B2C. This information can be viewed in the central monitoring system (TA RZ20).

5.2.7 Lean Basket Data Migration to NetWeaver 04

UseThis application supports you in the migration of data from the database of an existing ISA-installation running against a SAP J2EE Engine 6.20 (or a previous version) into the database of an SAP E-Commerce installation for SAP Web Application Server Java 6.40 (or higher). The legacy data is read from the 6.20 database and inserted into the 6.40 database. At the same time, data from the source database is implicitly modified to be compliant with the structure of the target database. The data in the old database is not changed during this process, thus the migration might be run several times.

5.2.8 Scheduler Administration

UseAs of SAP NetWeaver ’04, there is a Job Scheduler available for landscape-wide background processing in addition to the traditional local SAP background processing (transactions SM36/SM37)

5.2.9 Logging

UseThe ERP Java components use the standard logging and tracing from the SAP Web AS Java 7.00 server. The system writes logging and tracing messages into the central log files of the



SAP Web AS Java 7.00 server. You can use the Log Viewer, which is automatically installed with the SAP Web AS Java 7.00 server, to view the logs and trace files. You can change trace settings for specific locations and categories.

Logging is configured centrally in the Visual Administrator of SAP Web AS Java 7.00 (server service: Log Configurator).

For information search for Administration Manual Supportability and Performance Management Logging Log Configuration in http://help.sap.com.

5.2.10 VersionVersion information was moved to http://[hostname]:[port]/sap/monitoring/ComponentInfo, where [hostname] is the hostname and [port] the http of this J2EE Engine.

5.3 Modifying and Enhancement of the SAP E-Commerce Web Application Framework

For a detailed description of ISA modifications (e.g. changing the global look and feel of the Web Shop UI) see the standard guide SAP E-Commerce 5.0 - Development and Extension Guide.

To get the latest version, log on to the SAP Services Marketplace.

http://service.sap.com/erp-inst SAP ERP SAP ERP 6.0 Installation SAP E-Commerce 5.0 - Development and Extension Guide.

5.4 Restarting single Java Applications using the Visual Administrator

UseIn order for some changes to a java application configuration to become effective, the application needs to be restarted. Especially when changing XCM settings, a restart of the affected application is usually necessary. Throughout this guide, you will be advised to restart an application when needed.

Procedure1. Open the Visual Administrator by double-clicking on go.bat in the admin subdirectory of

your J2EE root directory (Windows path: \usr\sap\<SAPSID>\JC<xx>\j2ee\admin\go.bat).

2. Create a new configuration using the New button.

3. Enter a name for your connection to your SAP J2EE Engine (for example, The hostname of the J2EE server).

4. Choose Direct Connection to a Dispatcher Node.

5. Choose Next.

6. Fill out the fields as follows:

User Name <your username>

Host <your J2EE Host>

Port P4 Port of J2EE (usually HTTP Port + 4)





7. Choose Save.

8. Choose Connect.

9. Enter your password.

10. Choose Connect.

Wait until the connection process is finished.

11. Choose Cluster Server Services Deploy.

12. Select radio button Application.

13. Select a Java application to be restarted.

14. Choose Stop Application Ok.

15. Choose Start Application Ok.

5.5 Additional Installation Information on SAP E-Commerce for SAP ERP

Installation Guide: SAP ERP 2005 ( SR# ) ABAP+Java on <OS>:<DBMS>These guides describe the Installation of the Web AS Java and of the ERP Java components.

For every combination of the Database Management System (DBMS) and operating system (OS) an extra document exists.

You will find those guides under http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Installation → SAP ERP 2005 SR# - Installation Guides.

Just follow the ABAP+Java link in the desired DBMS/OS combination.

Installation Guide: SAP ERP ( SR# ) Java on <OS>:<DBMS>Those guides describe the Installation of the Web AS Java and CRM Java components.

For every combination of the Database Management System (DBMS) and operating system (OS) an extra document exists.

You will find those guides under http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Installation → SAP ERP 2005 SR# - Installation Guides.

Just follow the Java link in the desired DBMS/OS combination.

Upgrade Guide: SAP ERP 2005 ( SR# ) JavaThe same as the installation guide, but describes only the upgrade from ECO 4.0 to 6.40 with ECO 5.0.

You will find this guide under http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Upgrade → Upgrade Documentation - SAP ERP 2005 SR#.

Just follow the link for SAP ERP Central Component 6.0 SR2 ABAP in the desired DBMS/OS combination.






Upgrade Guide: SAP ERP ( SR# ) Java on <OS>:<DBMS>This upgrade guide describes the upgrade of the Java components during an upgrade from the basis J2EE 6.20 or below.

You will find these guides in the ERP area under http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Upgrade → Upgrade Documentation - SAP ERP 2005 SR#.

Just follow the link for SAP ERP 2005 SR2 Java Components in the desired DBMS/OS combination.

SAP E-Commerce 5.0 for SAP ERP - Bus. Scenario Config. GuideThis guide is an extract of the relevant ECO ERP chapters of the Solution Manager.

You will find those guides under http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Installation.

SAP E-Commerce 5.0 for SAP ERP - IPC Configuration GuideThis guide describes the configuration of the IPC in ECO ERP.

You will find those guides under http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Installation.

SAP Help PortalIn the Help Portal you will find the functional documentation of the components and function of ECO ERP.

The Business Scenario and Business Process documentation is only available in the Solution Manager (this is not part of the Business Scenario Configuration Guides).

You can access it at http://help.sap.com → SAP ERP → ERP Central Component (English).

To reach the ECO documentation, select in the menu on the left:

SAP ERP Central Component → Logistics → Sales and Distribution (SD) → Sales (SD-SLS) → ERP E-Commerce.

SAP E-Commerce 5.0 Development & Extension Guide You will find this guide at http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Installation.

SAP E-Commerce 5.0 – Examples & TutorialsThis guide contains examples and tutorials for the Development & Extension Guide.

You can access it at http://service.sap.com/erp-inst → SAP ERP → SAP ERP 6.0 → Installation.








Date post:	01-Nov-2014
Category:	Documents
Upload:	srinivasa-reddy
View:	133 times
Download:	8 times