SAP E-Commerce with SAP ERP (220)

rangaleclickΛογισμικό & κατασκευή λογ/κού

4 Νοε 2013 (πριν από 3 χρόνια και 9 μήνες)

913 εμφανίσεις



S
AP
ERP

6
.0

EhP3

August

200
8

English














SAP
E
-
Commerce

with

SAP ERP

(2
20)










SAP AG

Dietmar
-
Hopp
-
Allee

16

69190 Walldorf

Germany

Building Blo
ck Configuration Guide


SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
2

of
67

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
Cor
poration.

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, Web
Sphere, 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, WinF
rame, 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 registere
d 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, xA
pp, 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
a
nd 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 Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
3

of
67

Icons


Icon

Meaning


Cautio
n


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 i
ndividual 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 w
ell 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 th
ey appear in the documentation.

<Example text>

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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
4

of
67

Content
s

1

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 Pr
oduct 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 & Compo
nent 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

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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
5

of
67

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/Cu
stomer 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 Setting
s

................................
................................
...............

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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
6

of
67

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

................................
................................
..................

64

5.2.9

Logging

................................
................................
................................
.............

64

5.2.10

Version

................................
................................
................................
..............

65

5.3

Modifying an
d 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 Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
7

of
67

SAP
E
-
Commerce
with
SAP ERP (
2
20)
Configuration Guide


1

Purpose

The building block

SAP E
-
Commerce
with

SAP ERP

contains all configuration s
teps that are
required to set up the following business scenarios:



Sales Order Processing Business
-
to
-
Business



Sales Order Processing Business
-
to
-
Consumer



2

Preparation

SAP E
-
Commerce for
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 P
ricing and Configurator, TREX as Catalo
g and Search
engine and Web Server for document publication.



2.1

Prerequisites

The system landscape including all SAP
ERP

6.00
components as descr
ibed 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 854
1
70. How to

configure your SAP Virtual
Machine Container (VMC
)
is
described in
the configuration g
uide

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 you
r TREX Engine as described
in

the

i
nstallation
g
uide

Installation
-

Search and Classification TREX Single Host

in

http://service.sap.
com/instguidesnw70



Installation



Installation
-

Standalone
Eng
ines
.



Web Server:

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



2.1.1

SAP Notes

Before you

begin the installation or
configuration, read the relevant SAP Notes. These SAP
Notes contain important information
on

installation

of the building block
SAP E
-
Commerce
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

).

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
8

of
67

S
AP 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 a
bout the Product Catalog

The I
nternet product catalog is based on the data from the
Product Catalog

component in the
ERP

s
ystem.

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 dat
a 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.

Use

The following chapter contains very c
ommon entries. They are for demonstration purposes
only.

Procedure

1.

Access the activity using one of the following navigation options
:

Transaction code

WWM1

SAP
m
enu

Logistics


Materials Management


Product Catalog


Product Catalog


Create

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
9

of
67

2.

Enter the

name for your new product c
atalog.

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

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 Cur
rency your Web
shops should use

Display prices

select

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 var
iant for your catalog.

Setting

Value

Description


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 se
cond
language create a second variant and maintain later all
material descriptions in

the second language.
.

Setting

Value

Description


Variant

<Enter value>

Enter a unique ID for your
v
ariant

Language

<Enter value>

Specify the language for your
v
ariant

Currency

<Enter value>

Specify the currency for your
v
ariant

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
10

of
67

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


Please check the Delta Guide.

Procedure

1.

Access the activity

using one of the following navigation options
:

Transaction code

WWM2

SAP
m
enu

Logistics


Materials Management


Product Catalog


Product Catalog


Change

Layout
a
reas can be created either manually
,

or the
c
lassification
s
ystem could be used to
propo
se 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

Ent
er 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
a
rea.

6.

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

7.

Spec
ify if you want to
manage access authorizations for
the l
ayout
a
rea.

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 an
d mu
l
timedia objects can be assigned to individual items as well.
Assigning documents is described in
the
section
Document Management
.


3.1.2.3

Maintaining Additional Material Texts

Use

You can maintain additional text for each material
and for
the l
ayout
a
rea
tha
t you want to
display in your
w
eb shop. You can copy existing texts from the material master data (if they
are maintained), for example
,

sales texts.

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
11

of
67

Procedure

1.

Access the activity using one of the following navigation options
:

Transaction code

WWM2

SAP
m
e
nu

Logistics


Materials Management


Product Catalog


Product Catalog


Change

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 a
l
ayout
a
rea.

5.

Select a
m
aterial
,

a
nd 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 w
ant 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

Use

The documents for the product catalog are stored in a separate directory, which must be

accessible by HTTP.

Therefore
,

you can create a new directory <
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.

Procedure

Web Server

Creating the Direct
ory for Document Publication

1.

To check whether the directory
catalog

exists, open the directory
d
efault Web
s
ite in the
file tree structure

of The MS Internet Service Manager.
The MS Internet Service Manager
displays the subdirectories and the virtual dire
ctories mapped to the
d
efault Web

site.

2.

If you do not find the directory
catalog
attached to the
d
efault Web
s
ite, 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 choo
se
Properties
.

The tab
Home Directory

shows the path to the HTTP root directory in the field
Local Path
,
for example
,

C:
\
Inetpub
\
wwwroot
.

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
12

of
67

4.

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

5.

With the Wind
ows 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
optio
n
Share this folder
,

and enter the alias
catalog

in the field

share name.


3.1.3.2

Maintaining Properties of the Default Web Site

Use

After you ensure that the directory
catalog
exists as a subdirectory of the HTTP root directory,
you have to maintain the settings

for this directory in the MS Internet Information Server.

Procedure

Web Server

Maintaining Properties of the Default Web Site

1.

In the left window of the Internet Information Server, select the subdirectory
catalog
. Click
the right mouse button
,

and choose

Properties
:

2.

Choose the
Virtual

Directory

tab.

3.

Ensure that under
Access Permissions

the
Read
,

Write

and
Directory browsing

fields are
selected.

3.1.3.3

Setting of TCP

Port

Use

Because of security settings, it may be necessary to change default http port.

Usage of
default http port 80 could be
blocked within your network.

Procedure

Web 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
Prope
rties
:

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




SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
13

of
67

3.1.3.4

Copying Pictures to Folder on the Web Server


Please check the Delta Guide.

Procedure

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


3.1.4

Document Management

Through the
d
ocument
m
anagement a connection between the product catalog and the Web
server is created. Documents can be any kind of multim
edia
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 (
l
inks with the name of the pictures).

5.

You assign the
documents to the product catalog.


3.1.4.1

Creating Document


Please check the Delta Guide.

Use

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

s
ystem.

Procedure

For each material you ha
ve to run through the following procedure.

1.

Access the activity using one of the following navigation options
:

Transaction code

CV01N

SAP
m
enu

Logistics


Materials Management


Product Catalog


Environment


Document Manag
e
ment


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.

Cho
ose
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
i
nformation
d
ialog
b
ox.

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
14

of
67

11.

Choose
Create Original
.

12.

Enter
Applic
. LIM

13.

Enter
Original
. Just enter the fi
le name of your picture. For example,
<name.jpg>
or
<name.gif>
.

14.

Choose
Enter
.


15.

Confirm the
i
nformation
d
ialog
b
ox.

16.

Choose
Save
.


3.1.5

Assigning Documents to Product Catalog

Use

You can assign documents to the
Layout Area Level

(overview pictures) or to each
Mat
erial
(material pictures). For each material
,

you have to assign its document.

Procedure

1.

Access the activity using one of the following navigation options
:

Transaction code

WWM2

SAP
m
enu

Logistics


Materials Management


Product Catalog


Product Catalog



C
hange

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 a Layout Area.

5.

Select a Material.

6.

Double
-
click the
D

checkbox.

7.

Enter
L01

as type and the reque
sted document number as document.

8.

Choose
Enter
.

9.

Choose
Documents
, if you want to assign a picture on
l
ayout
a
rea
l
evel.

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 thi
s section
,

you can find general information about the settings for the Index Management
System (IMS).

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
15

of
67


The Index Management System itself is part of the
Text Retrieval & Information
Extraction

(TREX.)

The installation is part of the system setup and there
fore not described here.

For
more information on

the installation of the IMS
,

please
see t
he 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 i
nstallation
g
uide
SAP NetWeaver 2004s Standalone Engine Se
arch and

Classification (TREX) Single Host

fro
m
http://service.sap.com/instguidesnw70



3.1.6.2

Creating the Search Server Relation
(optional)

Use

Before you ca
n publish a product catalog
, you have to creat
e a
s
earch
s
erver
r
elation.

Procedure

1.

Access the activity using one of the following navigation options
:

Transaction code

SR
MO

IMG
m
enu

SAP NetWeaver



Knowledge

Management



Settings in the
Knowledge Warehouse

System



Text Retrieval & Information
Extrac
tion



Define Search Server Relation

2.

On the
Search Server Relation

tab
,

check whether an entry with a
s
earch 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
.

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
16

of
67

11.

Choose the
RFC destinations

tab.

12.

For the
s
earch
s
erver
r
elation
IMS_SSR
,

two entries should exist. One entry is for
indexing (I) and the othe
r 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
s
earch
s
ervice
r
elation entries.

14.

From the screen area
Search E
ngine

Settin
g
, choose
Connection Test
.

15.

Sometimes you have to restart the transaction
SRMO

before the connection test works.

Result

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

an
d
Version info for search eng.

contain entries.



3.1.6.3

Replication of Catalogs from an
ERP

Server to a
TREX Server

(optional)

Use

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

Procedure

1.

Access the activity using the following navigation option:

Transaction code

ISA_CAT_REPLICATION


You use the transaction
ISA_CAT_REPLICATION

(ABAP Report
ISA_CATALOG_REPLICATION) to replicate product catalogs from your SAP
E
RP

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
s
earch
s
erver
r
elation 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 param
eter. 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 replic
ating them
to TREX to single catalog areas. You can usually
execute the replication without flagging this
SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
17

of
67

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 informa
tion.

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
image
s 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 ch
ecked

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
-
speci
fic prices). Otherwise
deactivate this flag to improve replication
perfo
r
mance.

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. C
hoo
se
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
.




SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
18

of
67

3.1.6.4

Specifying the Address of the TREX Name Server

Use

Before 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
SA
P 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.

Procedure

Please refer to the installation guide
SAP NetWeaver 2004s Standalone Engine Se
arch 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

Use

Since 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

Use

Before you can maintain the XCM, you have to assign to your su01 user a s
pecial profile that
allows you the access to XCM. Then you can access the XCM with your E
RP

user and
password.

Procedure

1.

Access the activity using one of the following navigation option
s
:

Transaction code

SU01

SAP menu

Tools


Administration


User Mainte
nance


Users

2.

Enter your
User

and choose
Change
.

3.

Choose the
Roles

tab.

4.

Enter additional
r
ole
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 th
a
n the
client where you create your master
data.




SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
19

of
67

3.2.2

Generating Authorizations

Use

Internet User, Web Shop Manager and Super User
are

created in the following sections.

These users need special authorizations.
These are the collective roles. You have to check if
the single roles within the collective roles are generated.


Later
,

when the users are created
,

the roles will be assigned.

Roles

Users

SAP_ISA_UADM_RFC

User admin RFC user

SAP_ISA_UADM_MANAGER

User admin shop manager

SAP_
I
SA_UA
DM
_SUPERUSER

User admi
n 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

Ful
l B2B authorizations


Procedure

1.

Access the activity using one of the following navigation options:

Transaction code

PFCG

SAP

menu

Too
l
s



Administration



Administration


User
Maintenance


Role Administration


Roles

2.

Run through the following procedur
e 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.

Do
uble
-
click
the
single role.

Perform
the following steps for each single
r
ole assigned to
the collective
r
ole.

7.

Choose the tab
Authorizations.

8.

Check if the
Authorizations

tab is green. Otherwise generate the
Authorizations
.

9.

Choose
Display



Change
.

10.

Choose
Ch
ange Authorization Data
.

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
20

of
67

11.

Choose
Organizational levels…
(sometimes available)

12.

Choose
Full authorizations
.

13.

Choose
Transfer (Enter)
.

14.

Choose
Generate
.


3.2.3

The
Configuration

& Component Concept

Use

XCM offers you various configuration possibilities, including the p
ossibility to create customer
-

specific configurations.

E
ach component
, f
or example

JCO
,

can be assigned to a customer
-
specific
c
onfiguration
.
Y
ou can

therefore

set up your
Web

Application dynamically with the
c
omponents you need. For this guide
,

we want t
o set up a basic configuration with
ERP

connectivity
.

3.2.4

Creating
the Customer
-
Specific
Configuration

Use

Check if a customer
-
specific
c
onfiguration

has already been created by your system
administrator.

Otherwise
,

create a new
c
onfiguration according
to
the
following steps.

For example:

B2B
:

<YOUR_CONFIGURATION>

B2C:
<YOUR_CONFIGURATION>

Procedure

1.

Access the activity using the following navigation option:


Web browser

XCM

B2B URL

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

B2C URL

http://<host>:<port>/b2c/ad
min/xcm/init.do

Username

<Your User>

Password

<Your Password>

2.

Select the pre
-
configured SAP Configuration:

XCM Menu

Start



Application Configurations


SAP



r㍳瑡湤ar摰i† †



䍨潯s攠
Edit
.

4.

In the field
Create customer configuration based on this SAP

application configuration
,

e
nter 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.



I
f you are planning to use
the
TREX s
earch engine for storing your
E
RP

product catalog
,

choose r3standardpitrex

as pre
-
configured SAP Configuration.


SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
21

of
67

3.2.5

Configuring the
ERP

Connectivity

Use

The
ERP

Connectivity depends on two parts. First
,

you have to create an
RFC User

in the
ERP system
which i
s used by the Web
a
pplication to connect to the
ERP

system.
Second,
you assign that
u
ser to the
JCO

component.


3.2.5.1

Creating User WEBLOGIN

Use

In order to set up the connection from the
Web
a
pplication

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 ma
intained. It is important that the
email address is maintained, if you want to use the order confirmation via email.

Procedure

1.

Access

the activity

using

one of the following navigation options:

Transaction code

SU01

SAP
m
enu

Tools


Administration


User
Maintenance



Users

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

Func
tion

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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
22

of
67

5.

Choose
Save
.



3.2.5.2

Creating the JCO Component

Use

Y
ou have to define the connectivity to
the
ERP

s
ystem. 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
a
pplication and
the
ABAP
-
based
ERP

world. The procedure is the same as for
creating a customer
-
spe
cific
c
onfiguration.

Procedure

1.

Access the activity using the following navigation option:

Web browser

Creating the JCO Component

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.

Access the JCO Component:

XCM Menu

Start



Components



Customer



jco

3.

Choose
Edit
.

4.

E
nter a name for the new JCO component in the input field (for example,
<YOUR_JCO_CO
MPONENT
>)
,

and choose
Create
.

5.

Choose

B
ase
C
onfiguration
,
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 f
rom the JCO component of the
B2B/B2C
Configuration
.

JCO Access Data

client

The client used to log on to the SAP system

lang

Language (for example,
en

)

sysnr

System number of SAP system

ashost

Application server host name

passwd

Password for SAP syst
em. This password is encrypted when
it is stored. (for example,
welcome
)

user

User name (for example, WEBLOGIN)

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
23

of
67

maxcon

Maximum size of SAP Java Connector connection pool.

Jco.client.trace

Turns Jco trace on/off.

7.

Choose
Save configuration
.

8.

Test the conn
ection. Choose
Run test

in the
Configuration Test

dialog box. A window
appears,

and the connection data test should be
highlight
ed
in
green. If it is
highlighted in

red, an error occurred. In this case
,

check whether the user name and password of the
RFC U
ser

and the
JCO Component

are the same.

9.

Choose
Display

to switch to display mode.


3.2.6

Creating the Shop Component

(optional)

Use

Optionally,

you can configure your own shop component
.

You can also use the default for
B2B: r3shop_b2b and for B2C: r3shop_b2c.
W
e recommend this option, as y
ou can select
them later when you assign the components to the configuration.

Procedure

1.

Access the activity using the following navigation option:

Web browser

Creating the Shop Component

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.

Access the
Shop
Component
:

XCM Menu

Start



Components



䍵s瑯t敲e


Sh潰

3.

Choose
Edit to
s
witch to edit mode
.

4.

Create your own component by ent
ering 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 B2B

Shop scenario is Business to
Business (B2B) and backend
system is ERP
.

S
hopscenario

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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
24

of
67

Name

Value

Description

Object
-
Path

For example
:

D:
\
CRM4.0
\
shopadmin
\
r3shop

File system path that co
ntains
the ISA
ERP

shops

The file system path you use
for
s
hop
d
ata upload from the
file system to the J2EE DB.
This is o
nly relevant if you
perform an up
grade from
releases 3.1 or 4.0 otherwise
leave it blank.

Please use the administration
area of the
s
h
op
m
anagement
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
applica
tion.

defaultShopId


Shop Id for
d
efault
s
hop for
B2B, B2C and CCMS
Heartbeat

6.

Choose
Save configuration
.

7.

Choose
Display

to
switch

to display mode.



3.2.7

IPC Component

Use

As of CRM 5.0
,

the Internet Pricing and Configurator 7.0 is a component of the Applicat
ion
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



Instal
lation.




3.2.8

Creating the Web Catalog Component

Use

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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
25

of
67

Procedure

1.

Access the activity using the following navigation option:

Web brow
ser

Creating the Web Catalog Component

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.

Access the Web
c
atalog
c
omponent.

XCM Menu

Start


Components



Customer


w
ebcatalog

3.

Create your own component by entering a specific name in the input field (for example,
<
YOUR_CAT_COMPONENT

>), and choose
Create
.

4.

Make the following entries:

Name

Value

Description

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
i
mage to build the full
URL for the html 'img'
tag.

itemPageSize

5

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

numPageLinks

10

The number of page
links to be displayed in
t
he 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

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
26

of
67

Name

Value

Description

priceDecimalPlace

false

Parameter to dis
play or
hide decimal places for
Prices in the
WebCatalog

5.

Choose
S
ave configuration
.

6.

Choose
Display

to
switch

to display mode.

Result

Afterwards
,

you can access your new component as a subnode of Web catalog:

XCM Menu



Start



Components



Customer



w
ebc
atalog



<YOUR_CAT_COMPONENT>



3.2.9

Creating UI Component

Use

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

Procedure

1.

Access the activity using the following navigation option:

Web browser

UI Component Configuration

B2
B 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.

Access the
UI

component.

XCM Menu

Start


Components



Customer


ui

3.

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

4.

Make the following entries:

Name

Value

Description

language:

EN

Default Language for
User

interface and
Backend communication

enable.priceAnalysis:

true

Show or hide pric
ing
conditions display

configOnlineEvaluate:

true

Turn on IPC
configuration online
evaluation

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
27

of
67

Name

Value

Description

enablerelogincookie.core:

true

If enabled, a tempora
r
y
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 JS
P is
displayed.

exact.search.isacore:

true

perform an exact or non
-
exact search in the
product
-
list tab

maxhits.search.isacore:

${maxhits.search.isa
core.isa.sap.com}

Determines the maximal
number of hits for the
product
-
search

maxhits.search.action.busi
nesspartner:

${maxhits.search.acti
on.businesspartner.i
sa.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 s
pecified 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:

true

Enable personalization
for the application
configuration.

ui.fields.order.deliveryPriority:

editable

Visibility and
availability

of the field delivery
priority

ui.fields.order.shippi
ngCondition:

editable

Visibility and
availability

of the field shipping
condition

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
28

of
67

Name

Value

Description

ui.fields.order.bomExplosion:

hidden

Enable display of bill of
materials (BOM
explosion)

ui.fields.order.subitemDetailView:

hidden

Controls the enabling of
the sub items de
tail view

5.

Choose
Save configuration
.

6.

Choose
Display

to
switch

to display mode.

Result

Afterwards, 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
Co
nfiguration

Use

All the components created and maintained must be assigned to the customer
-
specific
c
onfiguration
. Then
the
web application

is able to determine all components that should be
used in your specific
c
onfiguration
.

Procedure

1.

Access the activit
y using the following navigation option:

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.

Access your customer
-
specific
c
onfiguration
:

XCM Menu

Start



Application Configurations


Customer


<YOUR_
CONFIGURATION
>

3.

C
hoose
Edit
.

4.

Choose
Display Advanced Settings
.

5.

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

Param.Name

Value

Component

J
co

data

<YOUR_JCO_COMPONEN
T>

JCO

I
pcjco

data

<YOUR_JCO_COMPONENT>

JCO

I
pc

data

ipcdefault

IPC

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
29

of
67

Param.Name

Value

Component

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_SU01User
ContactPerson (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
A
ctive Configuration.

7.

Check the
c
heckbox
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 dis
play mode.


3.2.11

Maintaining General Application Settings

Use

You
must

define specific parameters for the web application,
regardless i
f you are using SSL
or not.

Procedure

1.

Access the activity using the following navigation option:

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.

To carry out the activity, open the standard SAP Configurations:

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
30

of
67

XCM Menu

Start



General Application Settings



C
ustomer


b2b



b2bconfig


XCM Menu

Start



General Application Settings



Customer


b2c


b2cconfig


3.

C
hoose
Edit
.

4.

S
elect
false

for parameter
SSLEnabled

5.

Choose
Save
.

6.

Choose
Display
.

7.

After you performed all XCM Settings, r
estart your application.

8.

To res
tart, 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 (fo
r 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 Management

Users require an active Internet user to log on to the Web shop of the
web

application.

You
n
eed Internet users for the B2B and
B2C scenarios and for the shopadmin application to
create your Web shop.

You can create and maintain Internet users for your Web
-
based applications in the following
ways:




In your ERP backend system

For all ERP E
-
Commerce applications.





n the Web
-
based User Management application

For B2B ERP E
-
Commerce applications only


3.3.1

User Categories in User Management

In the XCM Application

of your B2B and B2C application
,

you can select the user type for
your Internet

user. For example, you can select that the B2B user logs on to the Web shop
with his
or her
c
ustomer
n
umber.

Possible user categories

Usertype

B2B

B2C

Shopadmin

R3_SU01User

X


X

R3_SU01UserStandalone

X


X

R3_SU01UserContactPerson

X



SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
31

of
67

Usertype

B2B

B2C

Shopadmin

R3_SU05Customer_
LoginCustomerNo

X



R3_SU05ContactPerson_LoginContact
PersonId

X



R3_UMESU01User

X



R3_UMESU01UserContactPerson

X



R3_UMESU01
UserStandalone

X


X

R3_SU01Customer_LoginEmail


X


R3_SU05Customer_LoginEmail


X



Two options are described below:




Use
rtype 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 documen
t
.


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
.

G
enerally
,

it is
recommended to use su01 user
, therefore skip this chapt
er.

Use

This transaction allows you to create
an
SU05 user with reference to a customer
and to
maintain user data (passwords
,

for example) in a table. Internet users are identified by:



User name and



User category

The Internet user information is client
-
de
pendent 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.

Procedur
e

1.

Access the activity using the following navigation option
:

Transaction code

SU05

2.

Enter the user ID and user category
KNA1
.

3.

Choose the following functions:

SAP Best Practices

SAP E
-
Commerce with SAP ERP (220): Configuration Gui
de


© SAP AG


Page
32

of
67

Create

The system returns the initial password for the Internet user.
Note the password if you wan
t 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.