WCEM 20 Module Config

SAP NetWeaver
How-To Guide
An extensive guide to WCEM 2.0

Modules' Parameters
Author: Simmaco Ferriero

Version 1.1
June 12
SAP NetWeaver
How-To Guide
© Copyright 2012 SAP AG. All rights reserved. Business Objects and the Business Objects logo,
BusinessObjects, Crystal Reports, Crystal Decisions, Web
No part of this publication may be reproduced or transmitted in any
Intelligence, Xcelsius, and other Business Objects products and
form or for any purpose without the express permission of SAP AG.
services mentioned herein as well as their respective logos are
The information contained herein may be changed without prior
trademarks or registered trademarks of Business Objects
notice.
Software Ltd. Business Objects is an SAP company.
Some software products marketed by SAP AG and its distributors
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
contain proprietary software components of other software vendors.
Anywhere, and other Sybase products and services mentioned
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and herein as well as their respective logos are trademarks or
Visual Studio are registered trademarks of Microsoft Corporation. registered trademarks of Sybase Inc. Sybase is an SAP company.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
System p5, System x, System z, System z10, z10, z/VM, z/OS, registered trademarks of Crossgate AG in Germany and other
OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, countries. Crossgate is an SAP company.
POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale,
All other product and service names mentioned are the
PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS,
trademarks of their respective companies. Data contained in this
HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,
document serves informational purposes only. National product
Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet
specifications may vary.
are trademarks or registered trademarks of IBM Corporation.
These materials are subject to change without notice. These
Linux is the registered trademark of Linus Torvalds in the United
materials are provided by SAP AG and its affiliated companies
States and other countries.
("SAP Group") for informational purposes only, without
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are representation or warranty of any kind, and SAP Group shall not
trademarks or registered trademarks of Adobe Systems Incorporated be liable for errors or omissions with respect to the materials.
in the United States and other countries. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements
Oracle and Java are registered trademarks of Oracle and its affiliates.
accompanying such products and services, if any. Nothing herein
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the should be construed as constituting an additional warranty.
Open Group. These materials are provided “as is” without a warranty of any
kind, either express or implied, including but not limited to, the
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, implied warranties of merchantability, fitness for a particular
VideoFrame, and MultiWin are trademarks or registered trademarks purpose, or non-infringement.
of Citrix Systems Inc. SAP shall not be liable for damages of any kind including without
limitation direct, special, indirect, or consequential damages that
HTML, XML, XHTML, and W3C are trademarks or registered
may result from the use of these materials.
trademarks of W3C®, World Wide Web Consortium, Massachusetts
SAP does not warrant the accuracy or completeness of the
Institute of Technology. information, text, graphics, links or other items contained within
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi- these materials. SAP has no control over the information that
you may access through the use of hot links contained in these
Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or materials and does not endorse your use of third party web pages
registered trademarks of Apple Inc. nor provide any warranty whatsoever relating to third party web
pages.
IOS is a registered trademark of Cisco Systems Inc.
SAP NetWeaver “How-to” Guides are intended to simplify the
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, product implementation. While specific product features and
BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry procedures typically are explained in a practical business
Storm2, BlackBerry PlayBook, and BlackBerry App World are context, it is not implied that those features and procedures are
the only approach in solving a specific business problem using
trademarks or registered trademarks of Research in Motion Limited. SAP NetWeaver. Should you wish to receive additional
Google App Engine, Google Apps, Google Checkout, Google Data information, clarification or support, please refer to SAP
Consulting.
API, Google Maps, Google Mobile Ads, Google Mobile Updater,
Any software coding and/or code lines / strings (“Code”)
Google Mobile, Google Store, Google Sync, Google Updater, Google
included in this documentation are only examples and are not
Voice, Google Mail, Gmail, YouTube, Dalvik and Android are intended to be used in a productive system environment. The
trademarks or registered trademarks of Google Inc. Code is only intended better explain and visualize the syntax and
phrasing rules of certain coding. SAP does not warrant the
INTERMEC is a registered trademark of Intermec Technologies correctness and completeness of the Code given herein, and SAP
Corporation. shall not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP
Wi-Fi is a registered trademark of Wi-Fi Alliance.
intentionally or grossly negligent.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings Disclaimer:
LLC. Some components of this product are based on Java™. Any code
Computop is a registered trademark of Computop change in these components may cause unpredictable and severe
Wirtschaftsinformatik GmbH. malfunctions and is therefore expressively prohibited, as is any
decompilation of these components.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP Any Java™ Source Code delivered with this product is only to be
products and services mentioned herein as well as their respective used by SAP’s Support Services and may not be modified or
logos are trademarks or registered trademarks of SAP AG in altered in any way.
Germany and other countries.
i
Document History
Document Version Description

1.1 Added some changes and a new section related to the gift cards.
1.0 First official release of this guide
ii
Typographic Conventions Icons
Type Style Description Icon Description

Example Text Words or characters quoted Caution
from the screen. These
include field names, screen Important
titles, pushbuttons labels,
Note
menu names, menu paths,
and menu options. Recommendation or Tip
Cross-references to other
documentation Example
Example text Emphasized words or

phrases in body text, graphic
titles, and table titles
Example text File and directory names and
their paths, messages,
names of variables and
parameters, source text, and
names of installation,
upgrade and database tools.
Example text User entry texts. These are
words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example Variable user entry. Angle
text> brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for
example, F2 or ENTER.
iii
Table of Contents
1. Business Scenario .............................................................................................................. 1
2. Background Information..................................................................................................... 1
3. Application settings ............................................................................................................ 2
3.1 Contact Scenario (B2B) vs. Consumer Scenario (B2C) .............................................. 2
4. Configuration Modules ....................................................................................................... 5
4.1 Article ........................................................................................................................... 5
4.2 Campaign ..................................................................................................................... 6
4.3 Catalog ......................................................................................................................... 7
4.4 Checkout .................................................................................................................... 10
4.5 Com.sap.checkout.processconfig .............................................................................. 11
4.6 Com.sap.common ...................................................................................................... 12
4.7 Comp.theme ............................................................................................................... 13
4.8 Complaintsandreturns ................................................................................................ 14
4.9 Customerinteraction ................................................................................................... 15
4.10 Customerprofiles ........................................................................................................ 16
4.11 Installedbase .............................................................................................................. 17
4.12 Instore ........................................................................................................................ 18
4.13 Liveassistance ............................................................................................................ 20
4.14 Loyalty ........................................................................................................................ 21
4.15 Myaccounts ................................................................................................................ 22
4.16 Mysupport ................................................................................................................... 23
4.17 Payment ..................................................................................................................... 24
4.18 Prodavailability ........................................................................................................... 25
4.19 Productrecommend .................................................................................................... 26
4.20 Productregistration ..................................................................................................... 27
4.21 Salestransactions ....................................................................................................... 28
4.22 Servicecontract........................................................................................................... 32
4.23 Servicerequest ........................................................................................................... 34
4.24 Storelocator ................................................................................................................ 35
4.25 Uicomponentconfig..................................................................................................... 37
4.26 User ............................................................................................................................ 38
5. Appendix 1 ......................................................................................................................... 40
5.1 Catalog  MDM Destination ...................................................................................... 40
5.2 Catalog  Catalog ID ................................................................................................ 41
5.3 Catalog  Pricing Procedure ..................................................................................... 42
5.4 Checkout  Delivery Types ....................................................................................... 43
5.5 Checkout  Checkout Profile Group ......................................................................... 44
5.6 com.sap.common  Sales Organization / Distribution Channel / Division ............... 45
5.7 Complaintsandreturns  Smart Form for Complaints and Returns .......................... 46
5.8 Complaintsandreturns -> Transaction Type for Returns / Complaints ....................... 47
5.9 Customerinteraction  Review profile ....................................................................... 48
5.10 Customerprofiles  Sender's E-mail ID..................................................................... 49
5.11 Installedbase  Business Partner Profile .................................................................. 50
5.12 Instore  Partner Function for In-Store Pickup Location .......................................... 51
5.13 Instore  Business Partner ....................................................................................... 52
5.14 Instore  Store Type ................................................................................................. 53
5.15 Instore  Default country........................................................................................... 54
iv
5.16 Productrecommend  Method schema ..................................................................... 55
5.17 Productregistration  E-Mail Template ..................................................................... 56
5.18 Salestransactions  Responsible Sales Organization .............................................. 57
5.19 Salestransactions  Cancellation Reasons .............................................................. 58
5.20 Servicecontract  Transaction Type for Service Contracts / Contract Quotations ... 59
5.21 Servicerequest  Transaction Type for Service / Information Requests .................. 60
6. Appendix 2 – How to setup gift cards ............................................................................. 61
6.1 Gift Card Setup Procedure ......................................................................................... 61
6.2 Mail Form Setup Procedure ....................................................................................... 65
v
An extensive guide to WCEM 2.0 Modules' Parameters
1. Business Scenario
With this document we are going to illustrate all the available modules for Web Channel Experience Management 2.0
(WCEM 2.0) and their parameters. We will explore each module and for each module we will list and explain all the
parameters needed for its configuration.
For the scope of this document we are only considering a landscape with both CRM and ERP; we will use MDM as
the catalog engine. This is the most common setup we can find around and the one that allows more WCEM
parameters to be used.
At the beginning of this document we will give a look at some general settings that we can change on a web shop like
the CRM server, the Logon Scenario and so on. There are actually two available scenarios that we can use: contact
scenario and consumer scenario. In the first case we need to specify the Type of Main Business Partner as well, while
for the consumer scenario this parameter is not needed.
Many of the parameters are also documented with some pictures taken from the underlying CRM back-end. In order
to access many of them you need to logon on the CRM back-end and use the SPRO transaction for exploring the IMG
configuration. All these pictures are collected in a special appendix at the end of this document. For some of those
parameters there is also a link that points directly to the related image.
2. Background Information
This document is intended for all who want to correctly configure a WCEM application. Quite all the parameters have
been fully detailed and for many of them we provided some self-explaining screen shots.
The user needs to have already acquired some knowledge on how to manage a web shop trough the Web Channel
Builder.
NOTE: The information contained in this document has been collected from our demo system. It’s possible of course
that many of the values for the parameters here reported will not fit for your particular case. So it’s always suggested
to double check if the values you are going to give to a particular parameters is the correct one or not.
June 2012 1
3. Application settings
Let’s give a look first to some of the application settings we can change in our web shop. You need to access the Web
Channel Builder (WCB) for your application and set it on the “EDIT” mode.
3.1 Contact Scenario (B2B) vs. Consumer Scenario (B2C)
June 2012 2
Scenario Parameter Values Hint
Contact/Consumer Back End i.e. “CRM Default” This setting determines whether the application connects to the SAP ERP or the
SAP CRM back-end system. The functions available differ depending on which
back-end system you choose.
Contact/Consumer Destination i.e. “YGZ_800” Here you select the destination that corresponds to your back-end system. This
information is defined in SAP NetWeaver Administrator.
Contact/Consumer Release i.e. “CRM 7.01”
Contact/Consumer Logon  Contact The logon scenario defines the circumstances under which the Web shop
Scenario Scenario customer logs on to the Web shop. You can choose between "Consumer
 Consumer Scenario" and "Contact Scenario":
Scenario
 The contact scenario defines the relationship between the Web shop
customer and another business partner. This means that the Web shop
customer acts as a contact on behalf of this business partner, which is
usually an organization.
 The consumer scenario defines that the Web shop customer acts as a
consumer on his or her own behalf.
Contact Type of Main Sold-To Party In a logon scenario of type "Contact Scenario" the default setting of the main
Business business partner type is "Sold-To Party", which cannot be changed.
Partner
Contact/Consumer User  ABAP Only This setting is used to determine which user data storage is used:
Storage  UME and ABAP
System  UME Only  If you activate "ABAP Only", the user management engine (UME) is not
involved, and all user and business partner master data is stored in the ABAP
backend. This also means that the user authentication is performed against
the ABAP back-end data only.
 If you activate "UME and ABAP", the user master data is also created in the
UME. This means that the user authentication is performed against the UME
data.
Caution: This setting requires that the UME is configured so that the UME
user storage is in the ABAP backend. Please check your UME configuration in
the Netweaver Administrator Web Application under https://:/nwa ->
Configuration -> Identity Management-> Configuration -> Data Source. The
content of field "Data Source" must be "ABAP System".
 If you activate "UME Only", the user data is stored in the UME, and the UME
data source must not be "ABAP System".
Contact/Consumer Application A URL that is used by Web shop customers to start an application, consisting of
URL protocol, host, port and application root (for example, http://myvm:50000/main).
Contact/Consumer Force i.e. “No” This setting defines that the complete Web Channel application is run with
HTTPS HTTPS protocol. This means that each HTTP request is redirected to an HTTPS
request. It is a prerequisite that the Web Application Server supports HTTPS.
Force HTTPS is a mechanism that can be used to improve the security of Web
sites by ensuring a secure connection.
Contact/Consumer Secure i.e. “No” The secure cookie attribute informs the browser whether a cookie should only
Attribute be sent using a secure protocol such as HTTPS or SSL. If this parameter is set
to "true", this setting applies to all application cookies that support this
parameter. A list of these cookies can be found in the Security Guide for SAP
Web Channel Experience Management on SAP Service Marketplace.
Since secure cookies are only sent via HTTPS, it is necessary to activate the
"Force HTTPS" setting for the Web Channel application. The "Secure Attribute"
setting will not be set if "Force HTTPS" is not activated.
Contact/Consumer HTTP Only i.e. “No” The HTTP only cookie attribute prevents application cookies from being
Attribute accessible in the browser by using client-side scripting, for example, JavaScript.
If this parameter is set to "true", this setting applies to all application cookies that
support this parameter. A list of these cookies can be found in the Security
Guide for SAP Web Channel Experience Management on SAP Service
Marketplace.
Contact/Consumer Allow i.e. “Yes” If you activate this setting, a user can still submit a configuration for approval even if
Warnings warnings were found during the validation checks. If you do not activate this setting,
the user must resolve any warnings before the configuration can be submitted for
approval.
June 2012 3
Scenario Parameter Values Hint

Contact/Consumer Authorization i.e. “Off” If you activate this setting, the back-end system starts a trace so that
Trace authorization checks are recorded. This can be used when creating user roles.
Contact/Consumer Ext. Service Here you can enter a prefix to be added to the name of external services that are
Prefix created by the authorization trace. This can help to differentiate between the external
services of different applications or scenarios.
June 2012 4
4. Configuration Modules
Now let’s give a look to all the available modules with their parameters. For each module we have created a table
where we have the Module ID, the name of the parameter, the possible values or an example of value (this is prefixed
with “i.e.”, the hint that you can find also on the web channel builder aside each parameter.
For some of these parameters the parameter’s name is also clickable and it will bring you to a screen shot where you
can get help about where you can find that parameter in the system.
4.1 Article1
Module ID Parameter Values Hint
Article Enable Enabled/Disabled If you activate this setting, Web shop customers select product
Graphical characteristics using graphical pushbuttons (for example, product
Pushbuttons images or color samples as pushbuttons) when viewing product
for Image- details in the product catalog. In this case, make sure that you assign
Determining product images (that is, icons) to generic article characteristics (called
Characteristics attributes in SAP NetWeaver Master Data Management) in the SAP
NetWeaver MDM Repository. If you deactivate this setting, Web shop
customers select product characteristics using dropdown lists. Note
that if the quantity of pushbuttons is large, we recommend that you
deactivate this setting. Regardless of your setting, when Web shop
customers change their selections of graphical product characteristics,
the system shows matching images. You set generic article
characteristics as image-determining on the SAP Easy Access screen
in the SAP CRM back end by choosing Architecture and Technology -
> Middleware -> Data Exchange -> MDM Properties of Generic Article
Characteristics.
Article Enable Text Enabled/Disabled If you activate this setting, Web shop customers select product
Pushbuttons characteristics using text pushbuttons (for example, for size and fit)
for when viewing product details in the product catalog. If you deactivate
Characteristics this setting, Web shop customers select product characteristics using
Not Set as dropdown lists. Note that if the quantity of pushbuttons is large, we
Image- recommend that you deactivate this setting.
Determining
Article Priority Limit 0 This setting is only relevant if you choose the category or combined
for Generic navigation mode in the Product Catalog module of Web Channel
Article Builder. You can enter a threshold or limit for priorities of generic
Characteristics article characteristics (called attributes in SAP NetWeaver Master
Data Management). The system shows product characteristics up to
and including the one you enter as the limit in this setting in the Web
shop. If you enter 100, the system does not use a limit and shows all
product characteristics. If you enter 0, the system shows no product
characteristics. You prioritize generic article characteristics from 1 to
100 (1 is the highest priority) on the SAP Easy Access screen in the
SAP CRM back end by choosing Architecture and Technology ->
Middleware -> Data Exchange -> MDM Properties of Generic Article
Characteristics.
1
Generic article can be supported only with a IS Retail Backend.
June 2012 5
4.2 Campaign
Campaign Enable Enabled/Disabled If you activate this setting, Web shop customers can manually enter a
Manual promotional code in the product catalog, the shopping cart, or at
Promotional checkout. Customers can manually enter only one promotional code at
Code Entry any given time.
Campaign Enable Enabled/Disabled If you activate this setting, the system applies campaign determination
Automatic in the product catalog and the Java cart. For example, the system
Campaign determines discount campaigns that are relevant for products, and
Determination then shows discounted prices. You make settings for automatic
in Product campaign determination in Customizing for SAP CRM under Customer
Catalog and Relationship Management -> Basic Functions -> Campaign
Java Cart Determination. This Web Channel Builder setting does not affect the
application of campaign determination in the back-end cart or the
checkout.
June 2012 6
4.3 Catalog
Catalog Server type  SAP NetWeaver This allows you to choose a server type that the Web shop will use to
Master Data access product master data that has been provided by a back-end
Management system. You can choose either of the following:
 TREX
 SAP NetWeaver MDM: Product master data provided by SAP ERP
or SAP CRM is stored in SAP NetWeaver Master Data Management
(SAP NetWeaver MDM) repositories on a dedicated server.
 Search and Classification (TREX): Product master data provided by
SAP ERP is stored on a Search and Classification (TREX) index
server.
Catalog MDM i.e. “MDM_IWDF8958” This is the name of the SAP NetWeaver destination that is used to
Destination connect to the MDM server. You can specify multiple destinations by
separating each one with a vertical slash (|).
Catalog Catalog ID i.e. “PCSHOP” This is the technical ID of the product catalog group node (first below
root) in the SAP NetWeaver MDM Data Manager. The node's children
will be displayed as catalog areas.
Catalog Display views  Block View If you activate these settings, the respective display modes become
 List View available under the "View" dropdown list.
Catalog Default One of the above The view you select here becomes the default catalog view for all Web
Display View shop customers.
Catalog Available i.e. “12,24,36” These values appear under the "Show" dropdown list and limit the
Number of number of products displayed on a page. Values must be separated by
Products per a comma.
Page
Catalog Select  Product ID Ascending If you activate these settings, the respective product sort modes
Available Sort  Product ID become available under the "Sort By" dropdown list.
Modes2 Descending
 Price Ascending
 Price Descending
 Rated Products
Ascending
 Rated Products
Descending
 Product Name
Ascending
 Product Name
Descending
Catalog Default Sort One of the above This is the default mode products are sorted by.
Mode
Catalog Product  BASE (basic text) This is the default text type supplied as the product description by the
Description  EYEC (basic eye- back-end product workbench.
Text Type catcher)
 INSP (inspection text)
 INTC (internal node)
Catalog Navigation  Area This allows you to choose from the following navigation modes for the
Mode3  Category product catalog:
 Combined
 Area: Shows the product catalog areas created in the SAP
NetWeaver MDM repository.
 Category: Shows the product categories imported from the back-
end system into the SAP NetWeaver MDM repository.
 Combined: Shows the product categories using a combination of
area mode and category mode. This enables you to structure
portions of the catalog by areas and others by areas and
categories.
Catalog Attribute i.e. “50” This is the priority number of the last attribute to be shown in the Web
Priority Limit shop. Category attributes are prioritized from 1 to 100, with 1 being the
highest priority. Attributes up to and including the one you specify are
2
if we use TREX/ERP then sorting by price and rated products are not supported
3
Category and Combined modes are not supported with TREX/ERP
June 2012 7

shown in the Web shop.
Catalog Number of i.e. “3” This is the number of values shown by default in the Web shop for each
Attribute attribute. Web shop customers can use a link to view more values.
Values to
Display
Catalog Pricing  List price This allows you to choose from the following:
Method  Dynamic pricing
 Mixed  List price: Price is determined by the product master condition
records maintained in the back end.
 Dynamic pricing: Price is determined by the Pricing Engine
(formerly Internet Pricing and Configurator (IPC)).
 Mixed: The pricing method adapts to the pricing scenario. For
example, dynamic pricing is used for campaigns.
The pricing method is pricing procedure-dependent, so you should verify the

dependency in the back end before making your selection.
Catalog Pricing i.e. “WECFOR” This is the pricing procedure used by the back end. You define pricing
Procedure procedures in Customizing depending on the back end:
 For SAP CRM under Customer Relationship Management -> Basic

Functions -> Pricing
 For SAP ERP under Sales and Distribution-> Basic Functions ->
Pricing -> Pricing Control -> Define and Assign Pricing Procedures
Catalog Dynamic  Net Value Without This is the dynamic pricing type you want to display in your catalog from
Pricing Type Shipping Cost the available price types returned.
 Gross Value Without
Shipping Cost
Catalog Condition i.e. “0PR0” This is the condition type to determine the base price.
Type for
Actual List
Price4
Catalog Condition i.e. “SAP004” This is the condition table to determine the base price.
Table for
Actual List
Price
Catalog Condition i.e. “0PR0” This is the condition type to determine the actual price.
Type for
Special List
Price
Catalog Condition i.e. “SAP004” This is the condition table to determine the actual price.
Table for
Special List
Price
Catalog Show Enabled/Disabled If you activate this setting, Web shop customers can see the
Strikethrough strikethrough price and discounted price of products in the catalog.
Prices
Catalog Show Enabled/Disabled If you activate this setting, Web shop customers can see the amount
Discounts that they can save on discounted products in the catalog.
Catalog Show Enabled/Disabled If you activate this setting, Web shop customers can see the percentage
Discount of the strikethrough price that they can save on discounted products in
Percentages the catalog.
Catalog Max. Number i.e. “100”
of Results
4
The List Price isn’t needed just for strikethough pricing. It can serve other purpose as well.
e.g. The special price is dependent on the user/business partner logged in, and will be taken (if available) from the
MDM condition record where the condition type = 0PR0, the condition table = SAP005, the sales organization = 0
50000001, the distribution channel = 30, the currency = USD, where the BP ID = ID of logged user and where the
validity is true compared to the actual date.
June 2012 8

Returned for
Products in
Advanced
Search
June 2012 9
4.4 Checkout
Checkout URL i.e. a valid URL Enter the URL called during checkout when Web shop customers select
to view the Web shop's terms and conditions.
Checkout Enable Enabled/Disabled If you activate this setting, Web shop customers can enter delivery
Delivery types in their checkout profiles and in their shipping details during
Types checkout. Web shop customers can use delivery types to enter a mode
of transport and transfer (for example, standard or overnight). You
define delivery types in Customizing depending on the back end:
 For SAP CRM under Customer Relationship Management -> Master

Data -> Business Partner -> Define Attributes -> Define Shipping
Conditions
 For SAP ERP under Logistics Execution -> Shipping -> Basic Shipping
Functions -> Shipping Point and Goods Receiving Point
Determination -> Define Shipping Conditions
Note that delivery types are called shipping conditions in both back
ends.
Checkout Delivery  Overnight Select the delivery types available to Web shop customers for checkout
Types5  Standard profiles and during checkout.
 Collect. processing
 Transport Service
 Just-in-time
 Synch. to production
 Sales returns
 TPVS Multimode
 Pick up
 Immediately
 ...
Checkout Default i.e. “Standard” Select the default delivery type for checkout profiles and checkout
Delivery shipping details. Web shop customers can enter different delivery types.
Type During checkout, the delivery type entered in the checkout profile is
used. If Web shop customers have not created a checkout profile, the
default delivery type defined in this Web Channel Builder setting is
used. To select a default delivery type, you must first activate it in the
list of delivery types.
Checkout Checkout i.e. “01” Assign a checkout profile group to the Web shop. When you assign the
Profile same checkout profile group to several Web shops, Web shop
Group customers can reuse their checkout profiles in each Web shop. Note
that you cannot assign more than one checkout profile group to a Web
shop. You make settings for checkout profile groups in Customizing
depending on the back end:
 For SAP CRM under SAP Web Channel Experience Management ->
E-Commerce -> Checkout Profiles
 For SAP ERP under Sales and Distribution -> SAP Web Channel
Experience Management -> Checkout Profiles
5
Delivery Types correspond to shipping Conditions in the back end, which in turn is a factor for determining the
shipping point/plant
June 2012 10
4.5 Com.sap.checkout.processconfig
com.sap.checkout.processconfig Export
configuration
June 2012 11
4.6 Com.sap.common
Com.sap.common Currency i.e. “USD”
Com.sap.common Sales i.e. “O 50000001” Enter the technical key for the organizational unit responsible for sales
organization and services that combines the relevant master data for customers,
products, and price lists. Check the organizational model in the back
end for the format.
Com.sap.common Distribution i.e. “30” Enter the technical key for the channel through which products or
Channel services reach customers. Check the organizational model in the back
end for the format.
Com.sap.common Division Enter the technical key for the organizational unit responsible for
products and services. Check the organizational model in the back end
for the format.
Com.sap.common Max. i.e. “1m” “1m” stays for “1 megabyte”

Allowed File
Size (Bytes
Com.sap.common Allowed File i.e. “txt,jpg,jpeg,png,pdf” Enter the file types (that is, the suffixes at the end of file names) for
Types attachments supported by the Web shop. To list multiple file types,
separate the file types with commas. If you do not enter at least one file
type, the system allows all file types. However, note that the system
might not be able to use all file types that you allow.
June 2012 12
4.7 Comp.theme
Comp.theme Allowed i.e. “sap/styles/sky”

Stylesheets “sap/styles/pebbles”
Comp.theme Allowed i.e. “sap/templates/jquery”

Rich
Render
Sets
June 2012 13
4.8 Complaintsandreturns
Complaintsandreturns Smart Form i.e. This is used when Web shop customers print the confirmation page
for “CRM_WEC_CR_PRINTFORM” after creating their complaint or return.
Complaints
and Returns
Complaintsandreturns Transaction i.e. “WECR” The default transaction type for returns is WECR.
Type for
Returns
Complaintsandreturns Transaction i.e. “WECC” The default transaction type for complaints is WECC.
Type for
Complaints
Complaintsandreturns Transaction i.e. “C001” This is the text that is used in the "Remarks" field when Web shop
Text Type for customers provide additional information for complaints and returns.
Remarks You select the text type in the back end when you define the text
determination procedure for complaints and returns transactions.
You define the text determination procedure in Customizing for SAP
CRM under Customer Relationship Management -> Transactions ->
Basic Settings -> Define Transaction Types. By default, entries in
Web Channel Builder match the standard delivery Customizing
entries. Any changes you make in Customizing should be replicated
in Web Channel Builder.
Complaintsandreturns Preceding  Order Items These are the options available to Web shop customers when they
Transactions  Installation choose a preceding transaction for a return.
for Returns Components
Complaintsandreturns Preceding  Order Items These are the types of preceding transactions available to Web
Transactions  Service Requests shop customers when they create a complaint. Order items and
for  Registered Products service requests are allowed by default for complaint creation, but
Complaints  Installation you must ensure the correct settings. You make these settings in
Customizing for SAP CRM under Customer Relationship
Components
Management -> Transactions -> Basic Settings -> Copying Control
for Business Transactions. For the consumer scenario you can also
allow registered products as preceding transactions, and for the
contact scenario you can have installation components available for
selection. However, it is not guaranteed that the product price
reflected in complaints based on registered products will be the
same as the price originally paid at the time of purchase.
Complaintsandreturns Enable Enabled/Disabled
Service
Contract
Determination
Complaintsandreturns Max. Number i.e. “100”

of Results
Returned for
Complaints
and Returns
in Advanced
Search

of Results
Returned for
Complaints in
Advanced
Search

of Results
Returned for
Returns in
Advanced
Search
June 2012 14
4.9 Customerinteraction
Customerinteraction Enable Enabled/Disabled If you activate this setting, Web shop customers can
Ratings post ratings and reviews for products. Ratings and
and reviews are always enabled or disabled together;
Reviews you cannot have one without the other.
Customerinteraction Moderate Enabled/Disabled If you activate this setting, product reviews by Web
Reviews shop customers are checked by a moderator to
Before ensure compliance with submission guidelines
Posting before being posted in the Web shop.
Customerinteraction Review i.e. “DFLT_PROF” This defines workflows for moderating reviews, and
Profile for checking reviews reported as inappropriate. A
default profile is defined in Customizing, and others
can be defined as required.
Customerinteraction Number of i.e. “10” This is the number of reviews to display per page in
Reviews the Reviews tab for a product.
Per Page
Customerinteraction Enable Enabled/Disabled If you activate this setting, a "Forums" link displays
Forums in the main navigation header.
Customerinteraction Forum i.e. Enter the home page URL to be used for forums.
Home “http://10.68.84.23:9001/community/forums/list.page” This is the entry point to the forum area provided by
Page URL the third-party software.
June 2012 15
4.10 Customerprofiles
Customerprofiles Sender's i.e. “WEC_NL” This is the ID of the e-mail address from which newsletter confirmation
E-mail ID e-mails are sent. You maintain this ID in Customizing for SAP CRM
under Customer Relationship Management -> Interaction Center
WebClient -> Agent Inbox -> Settings for Asynchronous Inbound
Processing -> Define Receiving E-Mail Addresses/Fax Numbers.
Customerprofiles Opt-In i.e. “Double Opt-In” This is the subscription type for newsletters.
Type
 With the opt-in subscription type, subscriptions are immediately
activated when Web shop customers save their newsletter
subscription profiles.
 With confirmed opt-in, customers receive a confirmation e-mail
when they save their profiles.
 With double opt-in, customers must first reply to their
confirmation e-mail to activate their subscriptions.
Note that it is not recommended to use the double opt-in type if you
allow the use of identical e-mail addresses for multiple customers.
Customerprofiles Attribute i.e. “NEW_SET_0000000551” This specifies which attributes and, if necessary, attribute values are
Set used to define personalized top n product lists.
June 2012 16
4.11 Installedbase
Installedbase Warranty i.e. “0”

Status
Warning
Threshold
(Days)
Installedbase Business i.e. “0000” This is the business partner profile that is used to determine a Web
Partner Profile shop customer's access to installed base components. You define the
business partner profile in Customizing for SAP CRM under Customer
Relationship Management -> SAP Web Channel Experience
Management -> E-Service -> Installed Base Management -> Define
Business Partner Profiles.
Installedbase Max. Number i.e. “100”
of Results
Returned for
Installed
Bases in
Advanced
Search
June 2012 17
4.12 Instore
Instore Enable In- Enabled/Disabled If you activate this setting, Web shop customers can order products for
Store in-store pickup. If you deactivate this setting, Web shop customers can
Pickup only check the availability of products in stores.
Instore Partner i.e. “ISTP” Enter the technical name of the partner function for in-store pickup
Function location (ISTP in the standard system). You define partner functions in
for In-Store Customizing for SAP CRM under Customer Relationship Management -
Pickup > Basic Functions -> Partner Processing -> Define Partner Functions.
Location
Instore Business i.e. “33” or blank You can enter a business partner for the system to use when Web shop
Partner customers search for stores for in-store pickup. If you do not enter a
business partner, the system uses the business partner assigned to the
sales organization that you entered in the Common Settings module of
Web Channel Builder. You create and edit business partners for
account management in SAP CRM.
Instore Store Type i.e. “CRME05” Select a store type, which corresponds to a relationship type in SAP
CRM. When Web shop customers search for stores for in-store pickup,
the system uses the store type for store searches. The standard setting
is CRME05.
Instore Show  Always If you activate "Always", the system always shows the exact quantity of
Exact  Based on Threshold product stock in the Web Shop after checking product availability. If you
Quantity of activate "Based on Threshold", the system only shows the exact
Product quantity of product stock when this number is equal to or less than the
Stock threshold for hiding the exact quantity of product stock. You enter the
number for the threshold in this module.
If you activate "Always", the system displays traffic lights as follows:

 Red indicates that product stock is 0
 Yellow is not used
 Green indicates that product stock is greater than 0
If you activate "Based on Threshold", the system displays traffic lights
as follows:
 Red indicates that product stock is 0
 Yellow indicates that product stock is less than or equal to the
threshold
 Green indicates that product stock is greater than the threshold
Instore Threshold i.e. “50” Enter the number of products for the system to use as a threshold to
for Hiding determine when to hide the exact quantity of product stock. When
Exact product stock is greater than the threshold, the system does not show
Quantity of the exact quantity of product stock. For example, you enter 50 for the
Product threshold. When product stock is greater than 50, the system shows the
Stock text "More than 50 PC available".
Instore Default for  All You can choose the default value of the dropdown list for the result list
Dropdown  Available that the system shows after Web shop customers search for product
List for availability, as follows:
Availability  All: The system shows all stores that match the search criteria,
Check
regardless of product availability. Note that the system only
Results
performs the availability check for the stores shown on the current
page.
 Available: The system only shows stores that match the search
criteria and where the product is available. Note that the system
must perform the availability check for all stores before showing
the result list.
Instore Show Enabled/Disabled If you activate this setting, when Web shop customers search for
Distances stores, the system shows distances to stores in ordered search results.
to Stores If you deactivate this setting, the system only shows stores matching
in Search the search criteria.
Results
Instore Distance  Miles Select the unit of distance used in the search results shown after Web
Unit  Kilometers shop customers search for stores offering in-store pickup.
Instore Use Web Enabled/Disabled If you activate this setting, when Web shop customers are logged on,
Shop the system uses Web shop customers' primary addresses shown under
Customers' My Account -> Settings -> Personal Data. When you enable the system
June 2012 18

Address to show distances to stores in this module, the system uses complete
Details as addresses. Otherwise, the system only uses the countries saved in
Default addresses. If you deactivate this setting, the system uses your settings
in this module for default country, default state or region, and default
city. Note that Web shop customers can only use address fields that
you have enabled in this module to search for stores for in-store pickup.
Instore Default i.e. “US” Enter the country for the system to display when Web shop customers
Country are not logged on. You define the list of countries to choose from in
Customizing for SAP CRM under Customer Relationship Management -
> SAP Web Channel Experience Management -> Basic Settings ->
Define Country Groups.
Note that if you want to enable Web shop customers to search by

country, you must also enable search by country in this module.
Otherwise, the system uses your entry for default country to limit
searches to this single country.
Instore Default Enter the key for the default state or region (for example, province) that
State or the system displays when Web shop customers are not logged on. You
Region define states or regions by assigning keys in Customizing for SAP CRM
under SAP NetWeaver -> General Settings -> Set Countries -> Insert
Regions.
Note that if you want the system to use your entry for default state or
region, you must also enable search by state or region in this module.
Instore Default Enter the city (as free text) for the system to use as default when Web
City shop customers are not logged on.
Note that if you want the system to use your entry for default city, you
must also enable search by city in this module.
Instore Enable Enabled/Disabled
Search by
Country

Search by
State or
Region
Search by
Postal
Code
Search by
City
Search by
Street
Instore Max. i.e. “50”

Number of
Results
Returned
for Stores
June 2012 19
4.13 Liveassistance6
Liveassistance Communications i.e. “10.16.224.73”

Server
Liveassistance Communications i.e. “1080”
Server Port
Liveassistance Default User i.e. “aquamarine”

Name
Liveassistance Communication i.e.

Channel “aquamarine_sales@bcmdemo.sap.corp”
Address
Liveassistance Make First Enabled/Disabled

Name
Mandatory
Liveassistance Make Last Enabled/Disabled

Name
Mandatory
Liveassistance Show First Enabled/Disabled

Name
Liveassistance Show Last Enabled/Disabled
Name
6
For Live assitance/chat a communication software like SAP BCM is a prerequisite.
June 2012 20
4.14 Loyalty
Loyalty Loyalty i.e. “ELOYALTY”

Program
ID
Loyalty Point Type i.e. “SBUPOINTS” This is the technical name of the point type used in the Web application.
Loyalty Enable Enabled/Disabled If you activate this setting, the number of loyalty points is displayed in
Decimal the Web shop with two decimal places; otherwise, the number is shown
Format for as an integer. If the decimal format for loyalty points is used in the SAP
Loyalty CRM back end, this setting is a convenient way of showing that format
Points to Web shop customers. Activating or deactivating this setting does not
change the number format that is configured in the back end.
Loyalty Enable Enabled/Disabled If you activate this setting, the loyalty program section is available in the
Loyalty in checkout to allow customers to redeem loyalty points.
Checkout
Loyalty General i.e. a valid URL

Terms and
Conditions
URL
Loyalty Show Enabled/Disabled If you activate this setting, Web shop customers can check their loyalty
Expiry transactions and see the expiry dates for points earned from
Information transactions.
June 2012 21
4.15 Myaccounts
Myaccounts Transactions  Service Requests

 Information Requests
 Service Contract
Quotations
 Complaints
 Returns
 Orders
Myaccounts Products and  Service Contracts
Service  Registered Products
Contracts
Myaccounts Settings  Credit Cards

 Personal Data
 Company Data
 Change Password
 Checkout Profiles
Myaccounts Preferences  Reviews
 Newsletter Subscription
 Loyalty Program
 My Profile
Myaccounts Personalization  Wish Lists
 Views
June 2012 22
4.16 Mysupport
Mysupport Service  Request a Service

Requests  Schedule a Service
 Request Information
Mysupport Complaints  File a Complaint
and  Return a Product
Returns
Mysupport Product  Register a Product
Registration
Mysupport Knowledge  Find a Solution

Base
June 2012 23
4.17 Payment
Payment Enable Enabled/Disabled If you activate this setting, Web shop customers can pay by invoice.
Payment
by Invoice
Payment Enable Enabled/Disabled If you activate this setting, Web shop customers can pay by credit card.
Payment
by Credit
Card
Payment Enable Enabled/Disabled If you activate this setting, Web shop customers can pay by cash on
Payment delivery (COD) (SAP CRM back end). If cash on delivery is the only
by Cash payment method that you activate for your Web shop, bear in mind that
on this payment method is not supported in combination with gift cards. If
Delivery you want to sell gift cards in your Web shop, you should offer another
payment method besides cash on delivery.
Payment Enable Enabled/Disabled If you activate this setting, Web shop customers can pay using payment
Payment service providers. You make settings in Customizing depending on the
Using back end:
Payment
Service  For SAP CRM under Customer Relationship Management -> SAP
Providers Web Channel Experience Management -> E-Commerce -> Payment
Service Providers
 For SAP ERP under Sales and Distribution -> SAP Web Channel
Experience Management -> Payment Service Prov.
Payment Default  Invoice Enter the default payment method for Web shop customers with no
Payment  Credit Card checkout profile.
Method  Cash on Delivery
 Payment Service Provider
Payment Credit  Diners Club Card Select the credit card types that Web shop customers can use in this
Card  American Express Web shop from the credit card types that you have defined in
Types  Master Card Customizing for SAP CRM or SAP ERP.
 PTAM
 PTMC
 VISA
Payment Enable Enabled/Disabled If you activate this setting, Web shop customers can pay for single
Multiple orders using more than one credit card.
Credit
Cards
Payment Payment  Datatrans Select the payment service providers that Web shop customers can use
Service  Paypal in this Web shop from the payment service providers that you have
Providers integrated in back-end Customizing
June 2012 24
4.18 Prodavailability
Prodavailability Show Enabled/Disabled

Rough
Stock
Availability
Prodavailability Show Enabled/Disabled

"Check
Quantity
Remaining"
Link
June 2012 25
4.19 Productrecommend
Productrecommend Enable Enabled/Disabled If you activate this setting, all Web shop customers can see the global
Global Top n top n product list in the product catalog. You must also create a target
Product List group.
Productrecommend Target i.e. “119” This is the target group for which a global top n product list is shown.
Group for The target group you select here must match the target group that you
Global Top n set in the IC WebClient top n list rule.
Product List
Productrecommend Enable Enabled/Disabled If you activate this setting, Web shop customers who are signed in can
Personalized see their personalized top n product list in the product catalog, based
Top n on their profile settings.
Product List
Productrecommend PPR Item i.e. “ZRKT” This is the item category used for partner/product ranges and top n
Category lists. Partner/product ranges are combinations of business partners
and products that are valid for a specific timeframe in a predefined
scenario. The PPR item category you select here must match that of
the top n rule you are using.
Productrecommend Show Enabled/Disabled If you activate this setting, Web shop customers can see pricing
Pricing information for top n product lists.
Information
Productrecommend Enable Enabled/Disabled If you activate this setting, Web shop customers can see product
Global proposals in the product details. Product proposals include related
Product products (cross-selling), alternative products (up-selling or down-
Proposals selling), and accessories.
Productrecommend Method i.e. “000011” This determines how to generate product proposals and how the
Schema results of the methods that are contained in the method schema must
be combined. You can find method schemas in Customizing for SAP
CRM under Customer Relationship Management -> Marketing ->
Product Proposals -> Define Method Schema (Expert).
Productrecommend Enable Enabled/Disabled If you activate this setting, Web shop customers who are signed in can
Personalized see personalized product proposals in the product details, based on
Product their profile settings.
Proposals
Productrecommend Show Enabled/Disabled If you activate this setting, Web shop customers can see pricing
Pricing information for product proposals.
Information
Productrecommend Method i.e. “000011” This determines how to generate product proposals and how the
Schema results of the methods that are contained in the method schema must
be combined.
You can find method schemas in Customizing for SAP CRM under
Customer Relationship Management -> Marketing -> Product
Proposals -> Define Method Schema (Expert).
Productrecommend Enable Enabled/Disabled If you activate this setting, Web shop customers can see product
Advanced recommendations obtained from analysis models created in SAP
Product NetWeaver Business Warehouse and transferred to SAP CRM.
Proposals Activating this setting also prompts you to provide the model ID.
Productrecommend Model ID This is the data mining model you created with the Analysis Process
Designer in SAP NetWeaver Business Warehouse.
June 2012 26
4.20 Productregistration
Productregistration Warranty i.e. “10”

Status
Warning
Threshold
(Days)
Productregistration Enable Enabled/Disabled
Registration
Confirmation
E-Mail
Productregistration E-Mail i.e. “DEFAULT CONF. E-MAIL”

Template
Productregistration Catalog ID This setting specifies the product catalog group node to use when
searching for registered products using product as a search criteria.
When you provide this ID, it allows Web shop customers to search for
their products in a catalog other than the one used in the Web shop for
browsing and ordering. This can be useful if, for example, a customer
is searching for a product that is no longer available for purchase in the
Web shop. If nothing is specified for this setting, the system uses the
catalog ID defined in the "Catalog" module.
June 2012 27
4.21 Salestransactions
Salestransactions Sales Office Organizational unit of a sales organization (for example, branch
office) responsible for sales and services in a geographic area. A
sales organization may have multiple sales offices.
Salestransactions Responsible i.e. “O 50000609” Enter the technical key for the organizational unit responsible for
Sales sales and services. Check the organizational model in the back end
Organization for the format. The responsible sales organization is always the finest
level of the hierarchy (for example, the sales organization itself or
often one of the sales offices).
Salestransactions Enable Enabled/Disabled Select the default document type (SAP ERP back end) / transaction
Creation of type (SAP CRM back end) to be used in the back end when a Web
Quotations shop customer creates an inquiry (SAP ERP back end) / request for
quotation (SAP CRM back end) in your Web shop. The settings are
defined in back-end Customizing
Salestransactions Show Enabled/Disabled The shopping cart preview displays products, quantities, prices, and
Shopping the order total.
Cart Preview
Salestransactions Enable Java Enabled/Disabled If you activate this setting, the Web shop uses the Java cart;
Cart otherwise it uses the back-end cart.
 With the Java cart, data is not stored directly in the back end,
but in the Java layer. Orders are only saved in the back end
when they are submitted (not before).
 With the back-end cart, data is stored directly in the back end.
Salestransactions Shopping i.e. “Standard UI” There are two types of UI available:
Cart UI  The standard UI displays the most important fields and enables
Web shop customers to complete orders fast.
 The extended UI displays more fields and provides more
information to Web shop customers.
You may combine either type of UI with either type of shopping cart
(Java cart or back-end cart).
Salestransactions Item i.e. “10” This setting is only relevant if you have enabled the Java cart. Enter
Increment an integer to set the increment used to number the items (or rows)
displayed in the shopping cart. We recommend that you enter the
same integer in Web Channel Builder and in back-end Customizing.
This ensures that the increment in the shopping cart and in checkout
are the same. You enter the integer in Customizing depending on the
back end:
 For SAP CRM under Customer Relationship Management ->
Transactions -> Basic Settings -> Define Transaction Types
 For SAP ERP under Sales and Distribution -> Sales -> Sales
Documents -> Sales Document Header -> Define Sales Document
Types
Salestransactions Maximum i.e. “99999999”
Order
Quantity per
Item
Salestransactions Days Used i.e. “1” This setting is only relevant if you have enabled the Java cart. Enter
to Calculate the number of days for the system to add to the current date to
Delivery calculate delivery dates. For example, if you enter the number 3, the
Date in Java system adds 3 days to the current date to calculate delivery dates.
Cart
Salestransactions Merge Enabled/Disabled If you activate this setting, the system merges identical items. That is,
Identical when Web shop customers add products to the shopping cart, the
Products system merges items that refer to the same product into single items.
Salestransactions Text ID of i.e. “1000” Enter the back-end text ID filled when Web shop customers enter text
Header Text in the "Your Message to Us" field in sales transaction headers.
You define text types in Customizing depending on the back end:
Basic Functions -> Text Management -> Define Text Objects and
Text Types (choose "Text Objects and IDs")
 For SAP ERP under Sales and Distribution -> Basic Functions ->
Text Control -> Define Text Types (choose "Header" under "Sales
June 2012 28

Document")
Salestransactions Text ID of i.e. “1000” Enter the back-end text ID filled when Web shop customers enter text
Item Text in the "Your Message to Us" field in sales transaction items.
You define text types in Customizing depending on the back end:
Basic Functions -> Text Management -> Define Text Objects and
Text Types (choose "Text Objects and IDs")
Text Control -> Define Text Types (choose "Item" under "Sales
Document")
Salestransactions Enforce Enabled/Disabled This setting is only relevant if you have enabled the Java cart. If you
Dynamic select list price as the pricing method in the "Product Catalog" module
Pricing in (for example, to increase performance), you can still activate this
Java Cart setting to use the Pricing Engine (previously known as IPC) for
(IPC Pricing) dynamic pricing in the shopping cart. Otherwise, the shopping cart
uses list prices from the product catalog. However, if you select
dynamic pricing in the "Product Catalog" module, the system always
uses the Pricing Engine for dynamic pricing in the shopping cart (this
setting is not required in this case). Note that when the product
catalog uses list prices, you must enforce dynamic pricing in the
shopping cart to ensure Web shop customers can view and change
shipping parameters (country, state or region, and delivery type) to
calculate estimated shipping costs in the shopping cart. Note that if
you display list prices in the shopping cart, only the following settings
are supported for the "Total Price" field under "Pricing on Shopping
Cart UI and Order UI": "Net Value" or "Gross Value". In this case, the
settings excluding shipping costs are not supported for the "Total
Price" field.
Salestransactions Reference i.e. “0000422292” This setting is only relevant if you have enabled the Java cart. You
Business must assign a reference business partner (SAP CRM back end) or
Partner or reference customer (SAP ERP back end) for pricing.
Reference You create this data depending on the back end:
Customer for
Pricing in  For SAP CRM, you create reference business partners on the
Java Cart WebClient UI under Account Management -> Accounts. You can
use the Sales Professional (SALESPRO) business role.
 For SAP ERP, you create reference customers in transaction
VD01.
Salestransactions Show Enabled/Disabled If you activate this setting, the system shows standard prices in
Strikethrough strikethrough font in the shopping cart when discounts apply (SAP
Prices CRM back end). The system shows strikethrough prices and actual
prices so that Web shop customers can determine savings. When
strikethrough prices and actual prices are the same, the system does
not display strikethrough prices.
Salestransactions Default order i.e. “WECO” Select the default transaction type (SAP CRM back end) or document
Type type (SAP ERP back end) used in the back end when Web shop
customers create orders in the Web shop. You make the settings in
back-end Customizing. Note that the system only supports sales
orders.
Salestransactions Enable Enabled/Disabled You can show and hide fields in the Web shop by making settings in
Dynamic the "Sales Transactions" module of Web Channel Builder (SAP CRM
Field Control back end or SAP ERP back end).
If you use the SAP CRM back end with the back-end cart, the system
dynamically shows and hides fields in the shopping cart (by default)
based on your settings in Customizing for SAP CRM under Customer
Relationship Management -> Basic Functions -> Authorizations.
 If you activate this setting and you use the SAP CRM back end
with the back end cart, the system also dynamically shows and
hides fields in checkout and in orders (including order
confirmations) based on your authorization settings.
 If you activate this setting and you use the SAP CRM back end
with the Java cart, the system does not dynamically show and
hide fields in the shopping cart, but does use your authorization
settings to dynamically show and hide fields in checkout and in
orders.
 If you need to improve system performance, we recommend
that you deactivate this setting
June 2012 29

Salestransactions Enable Enabled/Disabled
Cancellation
of Orders
Salestransactions Cancellation  Delivery date too late Select the cancellation reasons from which you want Web shop
Reasons  Poor Quality customers to choose when they cancel an order. If you select only
 Too Expensive one cancellation reason, this reason will be used by the system in the
 Competitor better background, it will not appear on the user interface. In this case, the
 Warranty button for canceling an order will appear on the order display page
 Credit Check Negative and with SAP ERP back end also on the search result list. If you
 Unreasonable Request select more than one cancellation reason, the Web shop customer
will see a dialog box in which to select the cancellation reason. In this
 Cust.to Receive
case, the button for canceling an order will appear only on the order
Replacement
display page, not on the search result list. You maintain cancellation
 Substituted Due to Product reasons in Customizing depending on the back end:
Proposal
 Backorder
Transactions -> Settings for Sales Transactions -> Define Reasons
 Transaction Is Being
for Rejection
Checked
 For SAP ERP under Sales and Distribution under Sales -> Sales
 Own the product already
Documents -> Sales Document Item -> Define Reasons for
 70 No Description Available
Rejection
 Leasing: Credit Memo
Salestransactions Enable Enabled/Disabled If you activate this setting, Web shop customers can change
Address addresses (bill-to address and ship-to address) in orders after
Changes in submission, provided the orders have not been billed or shipped yet.
Orders Changing addresses in orders is not possible with orders that use a
payment service provider as the payment method.
Salestransactions Total Price i.e. “Net Value Without Shipping Enter the basis (for example, subtotals) for the total price in the
Costs” shopping cart and in orders. The basis must be consistent with the
pricing procedure in the back end. You define pricing procedures in
Customizing depending on the back end:
Basic Functions -> Pricing -> Define Settings for Pricing -> Create
Pricing Procedure
Pricing -> Pricing Control -> Define and Assign Pricing Procedures
Note that unit prices are always net prices including both shipping
costs and discounts. When you enter "Net Value Without Shipping
Costs" in this setting as the source for total prices, unit prices still
include shipping costs.
Note that if you display list prices in the shopping cart, only the
following settings are supported for this field: "Net Value Without
Shipping Costs" or "Gross Value Without Shipping Costs". In this
case, shipping costs are not displayed. Please ensure that these
settings are consistent with the price settings in the catalog module.
Salestransactions Your Enabled/Disabled
Message to
Us
Salestransactions Promotional Enabled/Disabled

Code
Salestransactions Taxes Enabled/Disabled
Salestransactions Shipping Enabled/Disabled

Salestransactions Your Savings Enabled/Disabled
Salestransactions Order Total Enabled/Disabled
Salestransactions Overall Enabled/Disabled

Status
Salestransactions Shipping Enabled/Disabled
Status
Salestransactions Billing Status Enabled/Disabled
Salestransactions Created On Enabled/Disabled

Salestransactions Country Enabled/Disabled
Salestransactions State or Enabled/Disabled
June 2012 30

Region
Salestransactions Product Enabled/Disabled
Salestransactions Quantity Enabled/Disabled
Salestransactions Unit Enabled/Disabled
Salestransactions Description Enabled/Disabled

Salestransactions Total Price Enabled/Disabled
Salestransactions Gift Message Enabled/Disabled
Salestransactions Delivery Enabled/Disabled
Salestransactions Item Enabled/Disabled
Salestransactions Enable Price Enabled/Disabled You can use price analysis when you set up the Web shop to check
Analysis the pricing procedure by clicking the price analysis link for each item
in the shopping cart (SAP CRM back end). We recommend that you
deactivate the price analysis link before opening the Web shop to
Web shop customers.
Salestransactions Show Details Enabled/Disabled If you activate this setting, Web shop customers can click a link in the
shopping cart to show details about items (that is, line items or rows).
Salestransactions Hide Icon for Enabled/Disabled
Displaying
Subitems
Salestransactions Max. i.e. “100”

Number of
Results
Returned for
Orders in
Advanced
Search
Salestransactions Max. i.e. “100”

Number of
Results
Returned for
Quotations in
Advanced
Search
Salestransactions Enable Enabled/Disabled If you activate this setting, the advanced search for orders retrieves
Search for all orders for the sold-to party of the logged-on user, irrespective of
Orders the assigned sales organization or distribution channel.
Across Example: The search finds orders for the sold-to party of the logged-
Multiple on user that were created in your Web shop or the SAP CRM
Sales Areas interaction center (different distribution channels). Or the search finds
orders for the sold-to party of the logged-on user that were created in
different Web shops (different sales organizations).
If you deactivate this setting, the advanced search for orders only
retrieves orders for the sold-to party of the logged-on user that were
created in your Web shop, that is, orders created for the sales
organization and distribution channel assigned to the Web shop.
June 2012 31
4.22 Servicecontract
Servicecontract Service servicecontract.wcb.configuration.contactUsOverlayTextDefaultValue The text in this resource bundle displays

Contract when customers select "Contact Us"
Purchase from the available actions in the search
Instructions results for service contracts. You modify
this by means of a module
enhancement.
Servicecontract Options for  Years These are the options available to the
Extending  Quarters Web shop customer when choosing a
a Service  Months measure of time by which to extend their
Contract  Weeks service contract
Servicecontract Hide Enabled/Disabled

Expired
Service
Contract
Items in
Service
Contract
Details
Servicecontract Transaction i.e. “WSC”
Type for
Service
Contracts
Servicecontract Transaction i.e. “WSCQ”
Type for
Service
Contracts
Quotations
Servicecontract Level at  Contract Header Level This determines whether the search
Which to  Contract Item Level results list shows contract information
Show for the contract header level, or for
Search individual items within the contract.
Results for
Service
Contracts
Servicecontract Remaining i.e. “30” This indicates when the contract status
Number of changes to "Nearing Expiry Date",
Days to based on the number of days remaining
Trigger the in the contract.
"Nearing
Expiry
Date"
Status
Servicecontract Period i.e. “7”
During
Which
Service
Contract
Quotation
Is Valid
Servicecontract Unit of i.e. “Days”

Time for  Years
Period
 Months
During
Which
Service
Contract
Quotation
Is Valid

Expired
Service
Contracts
in Search
June 2012 32

Results

Expired
Service
Contract
Items in
Search
Results
Servicecontract Smart i.e. “CRM_WEC_SERVICE_CONTRACT” This is used when Web shop customers
Form for print the service contract.
Service
Contracts
Servicecontract Smart i.e. “CRM_WEC_SCQ_SMARTFORM” This is used when Web shop customers
Form for print the service contract quotation.
Service
Contract
Quotations
Servicecontract Smart i.e. “CRM_WEC_SC_SMARTFORM_ITEM” This is used when Web shop customers
Form for print information pertaining to an item
Service within the service contract.
Contract
Items
Servicecontract Smart i.e. “CRM_WEC_SCQ_SMARTFORM_ITEM” This is used when Web shop customers
Form for print information pertaining to an item
Service within the service contract quotation.
Contract
Quotation
Items
Servicecontract Max. i.e. “100”
Number of
Results
Returned
for Service
Contracts
in
Advanced
Search
Number of
Results
Returned
for Service
Contract
Items in
Advanced
Search
Number of
Results
Returned
for Service
Contract
Quotations
in
Advanced
Search
June 2012 33
4.23 Servicerequest
Servicerequest Maximum i.e. “250” This is the maximum number of characters that display in the table
Number of before the rest of the problem update is shown in an overlay.
Characters for
Problem
Update Table
Servicerequest Transaction i.e. “ESRV”
Type for
Service
Requests
Servicerequest Transaction i.e. “EIRV”

Type for
Information
Requests
Servicerequest Smart Form i.e. This is used when Web shop customers print the confirmation page that
for Service “CRM_WEC_SR_SMARTFORM” displays after they have finished creating their service request.
Requests
Servicerequest Smart Form i.e. This is used when Web shop customers print the confirmation page that
for Information “CRM_WEC_IR_SMARTFORM” displays after they have finished creating their information request
Requests
Servicerequest Number of i.e. “4”
Available
Categories
Servicerequest Enable Enabled/Disabled
Service
Contract
Determination
Servicerequest Max. Number i.e. “100”
of Results
Returned for
Service
Requests in
Advanced
Search
Servicerequest Max. Number i.e. “100”

of Results
Returned for
Information
Requests in
Advanced
Search
Servicerequest Catalog ID This setting specifies the product catalog group node to use when
searching for service requests using product as a search criteria. When
you provide this ID, it allows Web shop customers to search for their
products in a catalog other than the one used in the Web shop for
browsing and ordering. This can be useful if, for example, a customer is
searching for a product that is no longer available for purchase in the
Web shop.
If nothing is specified for this setting, the system uses the catalog ID
defined in the "Catalog" module.
June 2012 34
4.24 Storelocator
Storelocator Enable Store Enabled/Disabled

Locator
Storelocator Business i.e. “33” You can enter a business partner for the system to use in the store
Partner locator. If you do not enter a business partner, the system uses the
business partner assigned to the sales organization that you entered
in the Common Settings module of Web Channel Builder. You create
and edit business partners for account management in SAP CRM.
Storelocator Relationship i.e. “00” You define usage types and relationship type groups in Customizing
Type Group for SAP CRM under Customer Relationship Management -> SAP
Web Channel Experience Management -> Basic Settings -> Store
Locator.
Storelocator Show Enabled/Disabled If you activate this setting, when Web shop customers search for
Distances to stores, the system shows distances to stores in ordered search
Stores in results. If you deactivate this setting, the system only shows stores
Search Results matching the search criteria in search results.
Storelocator Distance Unit i.e. “Miles” Select the unit of distance for the search results shown after Web
shop customers search for stores.
Storelocator Use Web Shop Enabled/Disabled If you activate this setting, when Web shop customers are logged on,
Customers' the system uses Web shop customers' primary addresses shown
Address Details under My Account -> Settings -> Personal Data. When you enable
as Default the system to show distances to stores in this module, the system
uses complete addresses. Otherwise, the system only uses the
countries saved in addresses.
If you deactivate this setting, the system uses your settings in this
module for default country, default state or region, and default city.
Note that Web shop customers can only use address fields in Store
Locator that you have enabled in this module.
Storelocator Default Store You can enter the key (or indicator) for the default store type. System
Type behavior depends on whether you enable store type as a criteria for
searches in this module, as follows:
 If you enter a default store type and you enable searches

by store type, the system uses the default store type as the
initial entry in the dropdown list for store type.
 If you enter a default store type, but you do not enable
searches by store type, the system uses the default store
type when Web shop customers search for stores.
However, the system does not show the dropdown list for
store type.
 If you do not enter a default store type, but you do enable
searches by store type, the system shows a blank as the
initial entry in the dropdown list for store type. When Web
shop customers do not enter a store type (that is, they
leave the blank), the system searches using all store types.
 If you do not enter a default store type and you do not
enable store type for searches, then when Web shop
customers search for stores the system uses all business
partner relationship categories assigned to the relationship
type group in Customizing for SAP CRM under Customer
Relationship Management -> SAP Web Channel
Experience Management -> Basic Settings -> Store Locator
-> Define Relationship Type Groups. Note that you assign
the relationship type group to the Web shop in the Store
Locator module.
Storelocator Default Country Enter the country for the system to display when Web shop
customers are not logged on. You define the list of countries to
choose from in Customizing for SAP CRM under Customer
Relationship Management -> SAP Web Channel Experience
Management -> Basic Settings -> Define Country Groups.
Note that if you want to enable Web shop customers to search by
country, you must also enable search by country in this module.
Otherwise, the system uses your entry for default country to limit
June 2012 35

searches to this single country.
Storelocator Default State or Enter the key for the default state or region (for example, province)
Region that the system displays when Web shop customers are not logged
on. You define states or regions by assigning keys in Customizing for
SAP CRM under SAP NetWeaver -> General Settings -> Set
Countries -> Insert Regions.
Note that if you want the system to use your entry for default state or
region, you must also enable search by state or region in this module.
Storelocator Default City Enter the city (as free text) for the system to use as default when Web
shop customers are not logged on.
Note that if you want the system to use your entry for default city, you
must also enable search by city in this module.
Storelocator Display Store Enabled/Disabled If you activate this setting, the system displays search results for
Locator stores graphically on a map (otherwise, the system displays text
Graphically only).
Storelocator Determine Enabled/Disabled You must register and assign a geocoder in Customizing for SAP
Geocoordinates NetWeaver under General Settings -> Set Geocoding. You must also
in SAP CRM retrieve geocoordinates (transaction CRMM_ISA_GEOC).
Back End
Storelocator Max. Number i.e. “4”
of Results
Returned in
Store Locator
Search per
Page
Storelocator Path to i.e. Enter the path to the JavaScript file for integration of a map into Store
JavaScript File “sap/storelocator/ui/scripts/graphical- Locator. If you do not enter a path, the system does not use a map.
for Map map-script-google-example.js” If you have an agreement with Google Inc. to use the Google Maps
Integration API and you want to use the example implementation in the standard
delivery to integrate the Google map, enter the path
sap/storelocator/ui/scripts/graphical-map-script-google-example.js in
this field. The system displays a message on the Store Locator UI
warning you that the Store Locator is using an example map
implementation. If you want to remove this message from the Store
Locator UI, you must overwrite the isRenderExampleString method in
the GraphicalMapViewHandlerImpl view handler in the storelocator/ui
development component.
Note that you can also integrate a map from another vendor. For
information about extending Store Locator to integrate a map from
another vendor or for information about removing the warning
message from the Store Locator UI, see the Development and
Extension Guide - Application Information for SAP Web Channel
Experience Management on SAP Service Marketplace at
http://service.sap.com/wec-inst.
Storelocator Key for Map i.e. “gme-sapglobalmarketing1” If you activate the graphical store locator, you must enter a key (or
Integration client ID) for map integration. You get this key from an external
geocoder.
Storelocator Enable Search Enabled/Disabled
by Store Type
by Country

by State or
Region
by Postal Code

by City
Storelocator Max. Number 100

of Results
Returned in
Store Locator
Search
June 2012 36
4.25 Uicomponentconfig
Uicomponentconfig Maximum i.e. “30”

Number of
AJAX
Requests
That Lock
the UI
Uicomponentconfig Minimum i.e. “10”

Number of
AJAX
Requests
That Unlock
the UI
Uicomponentconfig Delay for i.e. “1300”

Feedback
Image in
Milliseconds
Uicomponentconfig Load Enabled/Disabled

JavaScript
Files
Globally
Uicomponentconfig Check i.e. “0”

Interval for
Templates
in Seconds
Uicomponentconfig Theme
Server
HTTP
Location
Uicomponentconfig Theme
Server
HTTPS
Location
June 2012 37
4.26 User
User Identification  E-Mail Address If you select an identification type, you specify the attribute that Web
Type shop customers should use, to log on to the Web shop.
 User Alias
Note: Once you have selected an identification type in the productive
 User Name
system, do not change this setting. A change would result in blocking
 Technical ID existing users from successfully logging on.
User Create User Enabled/Disabled If you activate this setting, a user and its business partner master data
in ABAP are created in the ABAP back end. If the logon scenario is a consumer
scenario, this setting is enabled by default, even if the user storage
system "UME Only" has been selected.
User Country  Europe If you select a country group, you define the countries from which Web
Group shop customers can come. You can assign countries to a country group
 Usa
in Customizing for Customer Relationship Management under SAP
 … Web Channel Experience Management -> Basic Settings -> Define
Country Groups. The reference user is assigned to new users that are
created for Web shop customers when they register to a Web shop.
The user for a Web shop customer inherits all of the reference user's
role attributes and authorization profile. The "Reference User" is a
mandatory field.
User Reference i.e. “WEC_REF” The reference user is assigned to new users that are created for Web
User shop customers when they register to a Web shop. The user for a Web
shop customer inherits all of the reference user's role attributes and
authorization profile. The "Reference User" is a mandatory field.
User User Group The users that are created when Web shop customers register to a
Web shop, are assigned to this user group. For more information about
user groups, see transaction SU01 in the SAP Easy Access screen.
User Validity of i.e. “7” The validity period defines, for how long, in days, the activation key is
Activation Key valid. The activation key is a URL that is sent in an e-mail to Web shop
customers when they register to a Web shop.
User Single Page Enabled/Disabled If you activate this setting, the registration process for Web shop
Registration customers is available on a single page instead of in a guided activity.
User Immediate Enabled/Disabled If you activate this setting, the users who register in the Web shop are
User activated, as soon as the registration process is completed.
Activation In the standard delivery, Web shop customers receive an e-mail that
contains a URL that they must click to activate their user.
User Registration i.e. “ACTIVATION_URL”
Confirmation
User User i.e. “ACTIVATION_URL”
Activation
User Customer i.e. “ZWC_CUSTOMER_VALID”
Validation
User Changed i.e. “FORGOT_PASSWORD”

Password
User Forgotten i.e. “FORGOT_USER”
User Name
User Enable Enabled/Disabled If you activate this setting, the security question is available in the Web
Security shop. The security question is used to authenticate Web shop
Questions customers who have forgotten their password.
User Security  Childhood Name
Questions
 Father’s Middle Name
 Mother’s Middle Name
 Place of Birth
User User  First Name If you select a field, this field is available in the Web shop. It must be
Authentication filled in by Web shop customers who have forgotten their logon
 Last Name
Fields information and request a new password or their user name.
 City
 Customer ID
User Enable Guest Enabled/Disabled If you activate this setting, Web shop customers can create an order in
June 2012 38

User Scenario the Java shopping cart without logging on and registering with the Web
shop.
User Reference i.e. “422279” The guest user scenario needs a reference that saves the transactional
Business data, and from which the guest user inherits all role attributes and
Partner authorization profiles. This reference is a "suspense account" that
varies depending on the back-end system:
 In the CRM back-end system a special business partner is

used as the "suspense account".
 In the ERP back-end system a CpD account is used as the
"suspense account".
June 2012 39
5. Appendix 1
This is a small appendix where you can find some screen shots that enable you to understand where to find some
important WCEM modules’ parameters in the back-end systems.
5.1 Catalog  MDM Destination
In ordert o manage the MDM destinations you can also access the following URL:
http://<servername>:<port>/mdm/destinations/
June 2012 40
5.2 Catalog  Catalog ID
June 2012 41
5.3 Catalog  Pricing Procedure
June 2012 42
5.4 Checkout  Delivery Types
June 2012 43
5.5 Checkout  Checkout Profile Group
June 2012 44
5.6 com.sap.common  Sales Organization / Distribution Channel /

Division
June 2012 45
5.7 Complaintsandreturns  Smart Form for Complaints and

Returns
June 2012 46
5.8 Complaintsandreturns -> Transaction Type for Returns /

Complaints
June 2012 47
5.9 Customerinteraction  Review profile
June 2012 48
5.10 Customerprofiles  Sender's E-mail ID
June 2012 49
5.11 Installedbase  Business Partner Profile
June 2012 50
5.12 Instore  Partner Function for In-Store Pickup Location
June 2012 51
5.13 Instore  Business Partner
With the transaction CRM_LOCMAP you can check the relationship between ERP plants and stores.
June 2012 52
5.14 Instore  Store Type
June 2012 53
5.15 Instore  Default country
June 2012 54
5.16 Productrecommend  Method schema
June 2012 55
5.17 Productregistration  E-Mail Template
This E-Mail template can be edited by accessing the CRM WEB UI with the “MarrketingPro” profile through the menu Marketing  Mail Forms:
June 2012 56
5.18 Salestransactions  Responsible Sales Organization
June 2012 57
5.19 Salestransactions  Cancellation Reasons
June 2012 58
5.20 Servicecontract  Transaction Type for Service Contracts /

Contract Quotations
June 2012 59
5.21 Servicerequest  Transaction Type for Service / Information

Requests
June 2012 60
6. Appendix 2 – How to setup gift cards

In this appendix you will find all the needed information to properly configure the gift card mechanism.
6.1 Gift Card Setup Procedure
1) Create your own Item Category and Item Category group in CRM
a. SPRO->CRM->Transactions->Basic Settings->Define item Category Group
b. Create an item category group GCNM
c. SPRO->CRM->Transactions->Basic Settings->Define item Category
d. Copy the item Category TAN to GCTN, maintain descriptions accordingly
e. Then Chose GCTN and Click on

f. Under Profiles -> Text Det. Proc. enter ORDER002 and Save
2) Define Item Category Determination in CRM

a. SPRO->CRM->Transaction->Basic Settings->Define Item Category Determination
b. Click on New Entries and Save
June 2012 61
3) Create the same Item Category Group and Item Category in ERP
a. SPRO->Sales and Distribution->Sales->Sales Document->Sales Document Item->Define Item Category
Group
b. Create New Entry Called GCNM, maintain suitable descriptions and Save
c. SPRO->Sales and Distribution->Sales->Sales Document->Sales Document Item->Define Item Category
d. Copy TAN to GCTN, maintain suitable descriptions and save.
e. SPRO->Sales and Distribution->Sales->Sales Document->Sales Document Item->Assign Item Category
f. Create New Entry like below and Save
4) Create Account Assignment Group, Account Key in ERP

a. SPRO->Sales and Distribution->Basic Functions->Account Assignment/Costing->Revenue Account
Determination->Check Master Data Relevant for Account Assignment
i. Choose Materials: Account Assignment Group
ii. Create a new Entry GC - Gift Cards, and then Save
b. SPRO->Sales and Distribution->Basic Functions->Account Assignment/Costing->Revenue Account
Determination->Define and Assign Account keys
i. Choose Define Account Key
ii. Create a new Entry GC: Gift Cards, and Save
c. SPRO->Sales and Distribution->Basic Functions->Account Assignment/Costing->Revenue Account
Determination->Define and Assign Account keys
i. Choose Assign Account Key
ii. Click on Position and look up for Pricing Procedure WECNUS and click OK
iii. Scroll Down to Locate Condition Type GC00 (Gift Card Redemption) and assign GC as the
Account Key
June 2012 62
d. SPRO->Sales and Distribution->Basic Functions->Account Assignment/Costing->Revenue Account

Determination->Assign GL Accounts
i. Now to set up the GL Account for Purchase of Gift Cards,
ii. Chose Combination Material Grp/Acct Key (Option 3)
iii. Create a new Entry
1. Application – V
2. Condition Type – KOFI
3. Chart of Accounts – CAUS
4. Sales Org – 3020
5. Account Assignment Group – GC
6. Account Key – ERL
7. G/L Account – 800001
e. Again go back to SPRO->Sales and Distribution->Basic Functions->Account Assignment/Costing-
>Revenue Account Determination->Assign GL Accounts
i. Now to set up the GL Account for Redemption of Gift Cards,
ii. Chose Combination Account Key (Option 5)
iii. Create a new Entry
1. Application – V
2. Condition Type – KOFI
3. Chart of Accounts – CAUS
4. Sales Org – 3020
5. Account Key – GC
6. G/L Account – 800001
5) Gift Card Settings in CRM
a. In CRM Go to TXN SPRO, Customer Relationship Management ->SAP Web Channel Experience
Management ->E-Commerce -> Gift Cards
June 2012 63
Gift Code Length – the length of the gift card code being sent in an email, it can be any number
MAIL Form ID – the Mail Form that you have created for sending out an email on purchase of gift card (when
you create mail form use attribute context as CRM_WEC_GC, to get the attributes for Gift Card into the email)
6) Assign Gift Card Set type to Product Category

a. In CRM go to transaction COMM_HIERARCHY
b. Chose Category From the dropdown and search for MAT_HAWA and Click on Start
c. Once you have the search results, Click on MAT_HAWA
d. Click on Change, and go to the tab Set types
e. Here add a new set type called CRM_GIFTCARD
f. Under View ID, enter SALES, and Save.
June 2012 64
7) Create Material in ERP for Gift Card

a. In ERP go to transaction MM01
b. Create a new material as a copy of any standard material(e.g. HT-1010),
c. Chose Industry Sector Aerospace and Defense, Material type HAWA
d. In Select View, chose the following Views, Basic Data 1, Basic Data 2, Sales Org Data 1, Sales Org Data
2, General Data/ Plant Data, Sales Text, Purchase Order Text, General Plant data/ Storage 1, General
Plant Data/ Storage 2, Accounting 1, Accounting 2, Costing 1, Costing 2
e. In Organization Levels Dialog box, mention Plant 3800, Storage Location 0001, Sales Org 3020,
Distribution Channel 30, and copy from the same set of data, (3800, 0001, 3020, 30)
f. Under Basic Data 1, give suitable Description, and under GenItemCatGroup, mention the Item
category group you have created (e.g. GCNM).
g. Hit enter to go to next tab,
h. Keep on Hitting Enter until you go to the tab Sales Org 2, here enter Account Assignment group
which you created above (e.g. GC), Item Category Group GCNM, and General Item Category Group
GCNM,
i. Keep on Hitting Enter to retain the default data until you get a prompt to save the material.
8) Now this material will flow to your CRM system,
a. Go to transaction COMMPR01 in CRM to open the gift card material you just created.
b. Go to tab Sales and Distribution, scroll down to the block with the title Gift Card Products
c. Click on Change material and maintain the following entries,
d. Save the Product
6.2 Mail Form Setup Procedure
Creating a Mail Form:

1. Login to the CRM UI using MARKETINGPRO business role
2. Click on Marketing work center Nav Bar
3. Under Create, click on Mail Form
4. Give an ID and description,
5. Chose the Attribute Context as “Gift Card Context” in order to get the attributes of Gift card in the mail form;
by clicking on the Attribute button, you can insert the desired attributes.
June 2012 65
June 2012 66
www.sdn.sap.com/irj/sdn/howtoguides

WCEM 20 Module Config

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

WCEM 20 Module Config

Caricato da

Copyright:

Formati disponibili

SAP NetWeaver

An extensive guide to WCEM 2.0

Author: Simmaco Ferriero

Document Version Description

Type Style Description Icon Description

Example text Emphasized words or

3.1 Contact Scenario (B2B) vs. Consumer Scenario (B2C)

Scenario Parameter Values Hint

Scenario Parameter Values Hint

Module ID Parameter Values Hint

The pricing method is pricing procedure-dependent, so you should verify the

 For SAP CRM under Customer Relationship Management -> Basic

Module ID Parameter Values Hint

 For SAP CRM under Customer Relationship Management -> Master

Com.sap.common Currency i.e. “USD”

Com.sap.common Max. i.e. “1m” “1m” stays for “1 megabyte”

Module ID Parameter Values Hint

Comp.theme Allowed i.e. “sap/styles/sky”

Comp.theme Allowed i.e. “sap/templates/jquery”

Complaintsandreturns Max. Number i.e. “100”

Complaintsandreturns Max. Number i.e. “100”

Complaintsandreturns Max. Number i.e. “100”

Installedbase Warranty i.e. “0”

If you activate "Always", the system displays traffic lights as follows:

Module ID Parameter Values Hint

Note that if you want to enable Web shop customers to search by

Instore Enable Enabled/Disabled

Instore Max. i.e. “50”

Liveassistance Communications i.e. “10.16.224.73”

Liveassistance Default User i.e. “aquamarine”

Liveassistance Communication i.e.

Liveassistance Make First Enabled/Disabled

Liveassistance Make Last Enabled/Disabled

Liveassistance Show First Enabled/Disabled

Loyalty Loyalty i.e. “ELOYALTY”

Loyalty General i.e. a valid URL

Myaccounts Transactions  Service Requests

Myaccounts Settings  Credit Cards

Mysupport Service  Request a Service

Mysupport Knowledge  Find a Solution

Prodavailability Show Enabled/Disabled

Prodavailability Show Enabled/Disabled

Productregistration Warranty i.e. “10”

Productregistration E-Mail i.e. “DEFAULT CONF. E-MAIL”

Module ID Parameter Values Hint

Module ID Parameter Values Hint

Salestransactions Promotional Enabled/Disabled

Salestransactions Shipping Enabled/Disabled

Salestransactions Overall Enabled/Disabled

Salestransactions Created On Enabled/Disabled

Salestransactions State or Enabled/Disabled

Module ID Parameter Values Hint

Salestransactions Product Enabled/Disabled

Salestransactions Quantity Enabled/Disabled

Salestransactions Unit Enabled/Disabled

Salestransactions Description Enabled/Disabled

Salestransactions Gift Message Enabled/Disabled

Salestransactions Delivery Enabled/Disabled

Salestransactions Item Enabled/Disabled

Salestransactions Max. i.e. “100”

Salestransactions Max. i.e. “100”

Servicecontract Service servicecontract.wcb.configuration.contactUsOverlayTextDefaultValue The text in this resource bundle displays

Servicecontract Hide Enabled/Disabled

Servicecontract Unit of i.e. “Days”