Config Guide ECO ERP 50

(1)

SAP E-Commerce for

mySAP ERP:

Business Scenario

Configuration Guide

(2)

Copyright

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

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

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

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

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.

(3)

Icons

Icon Meaning Caution Example Note Recommendation Syntax

Link to SAP Help Portal

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field

names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text _{Emphasized words or phrases in body text, titles of graphics and tables.}

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

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

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

Example text Exact user entry. These are words or characters that you enter in the

system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these

(4)

Important information regarding this document

This document is an extract of SAP Solution Manager configuration information from December 2005. Only business scenarios related to SAP E-Commerce for mySAP ERP are covered in this document. SAP Solution Manager is the main source of configuration information for all SAP solutions. In addition this supplementary document is provided for SAP E-Commerce for mySAP ERP customers as a one time effort.

Please note that any updates or corrections to SAP Solution Manager content as of December 2005 will not be included in this document.

This document will not be maintained by SAP.

Harmonized naming for SAP E-Commerce

To have one common name for SAP's E-Commerce applications we harmonized our naming.

The Commerce capabilities of mySAP CRM and mySAP ERP now share the common name "SAP E-Commerce".

SAP E-Commerce can be deployed with SAP CRM, SAP ECC (mySAP ERP) or with SAP R/3 back-end. If the context (back-end) is clear, the following name is used:

SAP E-Commerce

If the reference to used back-end is important, the following names are used: SAP E-Commerce for mySAP CRM

SAP E-Commerce for mySAP ERP

The term "SAP Internet Sales (R/3 Edition)" is replaced by "SAP E-Commerce for mySAP ERP". It will be used synonymously also in cases where you use the SAP E-Commerce application together with an SAP R/3 back-end. Only if there is an important difference between handling of an ERP or R/3 back-end, the term "SAP E-Commerce for SAP R/3" is used.

However the current name for the CRM Key Capability remains as mySAP CRM E-Commerce. The usage of the name "SAP Internet Sales", "SAP Internet Sales in mySAP ERP" and "SAP Internet Sales (R/3 Edition)" will be discontinued.

You will still find the former names in certain areas of the documentation as the new naming conventions will only be used when new documents are produced or adapted.

(7)

SAP E-Commerce for mySAP ERP 5.0:

Business Scenario Configuration Guide

1 Purpose

The ERP E-Commerce: Business Scenario Configuration Guide contains all of the configuration steps that are required to set up the following business processes for ERP E-Commerce:

Auction Payment and Delivery Processing in ERP E-Commerce Billing in ERP

Browsing For and Selecting Products in ERP

Inquiry Processing for Internal Users in ERP E-Commerce Inquiry Processing in ERP

Interactive Configuration

Managing Auctions for Selling via eBay in ERP E-Commerce Managing Catalog Content in ERP

Quotation Processing in ERP

Sales Order Processing B2B for Occasional Users in ERP E-Commerce Sales Order Processing B2B in ERP E-Commerce

Sales Order Processing B2C in ERP E-Commerce

Sales Order Processing for Internal Users in ERP E-Commerce Sales Order Processing one-Step Business in ERP E-Commerce . Web Analysis in ERP

Web Site Monitoring in ERP

2 Configuration

2.1 ERP E-Commerce System Prerequisites

The following table contains an overview of the technical components needed for ERP E-Commerce. The table displays the minimum and maximum releases for the components, and whether they are mandatory or optional.

Technical

Component Functions of Component (within scenario) Minimum Release Maximum Release Classification R/3 Server All scenarios 4.6c SAP ECC 6.0 Mandatory Plug-In for OLTP Data Exchange R/3 4.6c,

R/3 4.7, ERP 2004 PI 2004.1 SP10 Part of SAP ECC 6.0 Mandatory for R/3 4.6c, R/3 4.7, ERP 2004. In SAP ECC 6.0 it is not necessary as it is integrated in the SAP ECC 6.0. SAP BW Business Information

Warehouse BW 3.5 BI Content 3.5.2 Add-on BW 7.0 BI Content 7.0.2 Add-on Optional CRM Java Applications, CRM Java Components E-Selling 5.0 5.0 Mandatory

(8)

Technical Component Functions of Component (within scenario) Minimum Release Maximum Release Classification SAP Shared Java

Applications SAP Java Dictionary IPC, Workforce Deployment, E-Selling, Channel Management 5.0 5.0 Mandatory

SAP Shared Java Components SAP Shared Web Components CRM IPC Mobile IPC, Workforce Deployment, E-Selling, Channel Management 5.0 5.0 Mandatory if the Java components are modified in the NWDI

Tealeaf Tealeaf Java API 3.1 4.5 Mandatory if the Java components are modified in the NWDI STRUTS Struts API 1.2 1.2 Mandatory if the

Java components are modified in the NWDI J2SE, Java

Development Kit Java Virtual machine to run the software J2SE 1.42_08 J2SE 1.42_08 Mandatory SAP Web AS

Java

Provides the servlet engine

7.0 7.0 Mandatory TREX Search Engine and

Textmining Engine TREX 7.0 TREX 7.0 Optional IPC on separate

AP box 7.00 7.0 Optional.

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

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

B2B: 1024 * 768 pixel

B2C: 800 * 600 pixel

2.2 Configuring the Web Application

2.2.1 Extended Configuration Management (XCM)

Use

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

(9)

The CRM Web applications are used in the following scenarios: CRM E-Commerce

ERP E-Commerce

Selling via eBay in CRM and ERP Channel Management

Interaction Center

Interaction Center WebClient

Interaction Center Workforce Management Internet Customer Self-Service

SAF

You only have to set up XCM configuration settings for those Web applications that are relevant to the scenarios and processes you are using.

The XCM user interface is used for Java-side configuration of the Web application. You have to maintain two setting types in XCM:

General Settings

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

Additional Web application configuration settings

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

Not all applications support multiple application configurations. Some only support general settings. Some Web applications can run different configurations in different client sessions simultaneously. Each Web application provides one or more predefined (SAP) configurations, which you can find under

Start → Application Configurations → SAP. You create a new customer configuration based on these

predefined configurations and adjust it to your requirements. You then find your customer configuration under Start → Application Configurations →Customer. Each customer configuration contains:

A configuration name

Base configurations (from SAP on which you base your configuration)

A number of configuration parameters with associated values which you adjust.

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

Procedure

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

(10)

Starting XCM

1. You access the XCM tool at: http://<host>:<port>/<web app name>/admin/xcm/init.do

You can also start XCM in accessibility mode (according to Section 508 Rehabilitation Act) at the following URL: http://<host>:<port>/<web app name>/admin/xcm/init.do?sap-accessibility=x

2. Provide a user and password. If you are logging on for the first time use the Administrator user. the password you defined during the installation of NetWeaver

We recommend you create new users with lesser rights than the Administrator fort he administration of Web applications. See the SAP CRM Security Guide section E-Commerce for further details.

3. When the application opens a closed control tree is displayed on the left of the screen. A screen containing help information is displayed to the right.

You can use edit (change settings) or display (see settings) mode in XCM. You use the button in the top right hand corner of the screen to change between modes. When you switch to edit mode a DB lock is set meaning that only this user can edit the settings at one time. The lock is released once the user switches back to display mode or after session timeout (default timeout is 30mins).

Printable Help

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

General Settings

You set the general settings and they are valid for the whole Web application. Proceed as follows

:

1. Choose the Edit mode and select Start → General Settings → Customer. The system displays the

available nodes categorizing the general settings. Depending on the application you will have one or more tree nodes. For information on the possible settings, see the printable help information. 2. Expand a configuration node and select the right hand configuration node to see possible

configuration parameters in the right hand window.

3. Select a parameter and enter the settings values that meet your requirements. Each parameter contains a help description for information on what you need to enter.

Some parameters have default values set. When you change the values of these default parameters the system will mark them orange. You can revert back to the original default entry by selecting R (revert). 4. Select Save Configuration.

(11)

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

If your application does support multiple configurations, see the section below Multiple Application Configurations.

Multiple Application Configurations

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

Delivered SAP Configuration

You need to find out which SAP application configurations are delivered. In more complex applications, for example CRM E-Commerce, there are several pre-configured applications. In simpler applications, for example the User Management application, there are normally fewer, or only one, applications

configurations. You display the list in the pre-configured scenarios under Start → Application

Configurations → SAP in the control tree. Look through the configurations and choose the one that most

suits your requirements.

Create a Customer Application Configuration

Once you have selected the configuration that suits your needs go to Edit mode. 1. Enter a configuration Name and choose Create.

2. Configure the application configuration by associating configuration data with the configuration parameters. There is a description for the scenario of each configuration parameter in the last column of the parameter table.

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

Settings.

Configure a Customer Application Configuration

Once you have created the application configuration you need to configure it by changing the parameter values.

1. Select Configuration Documentation to see a list of the parameters to be configured.

2. Select a parameter and use the dropdown list box to assign a value. You can display a description of possible values by selecting the ? help button next to the drop down list box. If there is more details description for a parameter an additional ? button is displayed. 3

(12)

Static Values

Values that can be selected from a dropdown list box.

These values do not have a button in the Component Configuration column. Values based on Component Configuration

You first have to configure a component, for example a connection to your SAP CRM system, before assign the configured value to the parameter. These parameters have a button in the

Component Configuration column. For example the jco button for configuring connection parameters to the SAP system

If no value is assigned to these parameters you have to create a new component configuration. For more information see the section Creating a New Component Configuration.

If a value is assigned, it is most likely you will not have to change anything during the installation.

Creating a New Component Configuration

A component is an independently configurable part of the application (for example the jco component which enables connections between the SAP system and the Web application). A component can have several configurations, for example to different systems and clients. You assign one of the component configurations to the parameter in the application configuration. We recommend you create the component configuration at the same time as you set up the application configuration.

1. Select an empty entry in the dropdown list box for the parameter or choose create component

configuration. The system switches to the component creation screen. The correct component, for

example jco, is selected automatically and the system display a description of the use of the component.

2. Enter a name for the component configuration (for example Q5C_505 for the Q5C system with client 505) and choose Create. The application switches to the component configuration parameters screen.

3. Select a base configuration from the Base Configuration dropdown list box. A description is displayed using the ? button.

4. Enter values for the component configuration parameter and choose Save Configuration. Test your values in the Configuration Test area.

Testing a Component Configuration

Once you have created the component configuration, save it and test it as follows.

1. Select the test from the Select Test dropdown list box for the configuration. You can see a description by selecting the ? button.

2. Choose Run Test.

3. The system displays the test results in a new window. A red traffic light indicates the test failed and you must redo the configuration. A green traffic light indicates the test was successful.

4. Return to the application configuration, by selecting Back to Application Configuration and select the newly created configuration from the dropdown list box and assign it to the scenario parameter.

(13)

Define a Default Application Configuration

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

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

Save the Application Configuration

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

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

A red icon indicates the configuration is disabled.

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

Activating the Application Configuration

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

1. Start the J2EE Visual Administrator.

2. Connect to the SAP Web AS Java 7.0 server.

3. Choose Server node → open services node → Select deploy service → application and stop and

start the Web application.

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

Running the Web Application

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

(14)

Use the default configuration. Simply start the application and the configuration you set as default will be used. If you have just one configuration this will automatically be the default. For example if you want to call up the default configuration for the b2b Web shop the URL will look as follows:

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

Specify the application configuration name as a request parameter. In this case you run the application using a different application configuration to the default. You pass the name of the application configuration sing the request parameter configuration.xcm when calling the application. The scenario name is case sensitive. For example if you want to call up the application configuration myB2BCRM the URL will look as follows:

http://<host>:<port>/b2b/b2b/init.do?configuration.xm=myB2BCRM

Display a start up page containing links to all active configurations and starting the specific application configuration by using the link.

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

General Settings → <Web application name> → show.start.jsp.

Uploading and Downloading XCM Settings

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

Component configuration data Application configuration data

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

Downloading XCM Configurations

This enables you to download XCM configuration form the SAP Web AS Java 7.0 database to XML files. Proceed as follows:

1. Select the download button for the component configuration data file. The system generates a file named config-data.xml containing all component configuration data saved for the Web application. 2. Select the download button for the application configuration data file. The system generates a file

named scenario-config.xml containing all application configuration data saved for the Web application.

Uploading XCM Configurations

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

1. Select the Edit button.

2. The system displays two file input fields in the upload section.

3. Specify the config-data.xml (component configuration) and scenario-config.xml (application configuration) files, with complete file system paths for both files, and select Upload.

(15)

For the b2b and b2c Web applications in SAP E-Commerce the XCM administration tool provides a switch to a separate maintenance view for the IPC-specific part of the application (see IPC Switch for

XCM Configuration of SAP E-Commerce below). When switching to IPC you can up and download the

IPC application and component configurations. The IPC application configuration file is ipcscenario-config.xml, the component configuration file is ipcconfig-data.xml.

If you intend to transport XCM when doing a system copy within the CRM 5.0 release, refer to the chapter

Data Storage Security in the CRM Security Guide for E-Commerce.In addition to the XCM data you have

to also transport encryption keys used in Secure Storage of the SAP Web AS Java 7.0 engine.

Web applications based on CRM 4.0 do not save XCM settings in a database and they do not support the upload and download functionality described in this section. In CRM 4.0 the XCM settings are saved as XML files (config-data.xml for component configuration and scenario-config.xml for application

configurations) in a dedicated directory of the J2EE servers file system. You can find the location of the files in XCM Administration under Start → Options. You can upload these configuration files from CRM 4.0 to CRM 5.0 during an upgrade.

After migrating XCM settings from an older to a newer Web application version you must check if any of the customer-made XCM settings are obsolete see Indication of Obsolete XCM settings below). The new version may require you to change or give you the option of maintaining additional XCM settings. You add these settings manually, as described in the section Configure a Customer Application

Configuration above.

Indication of Obsolete XCM Settings

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

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

Components (marked with an exclamation mark on yellow background)

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

IPC Switch for XCM Configuration of SAP E-Commerce

The SAP E-Commerce B2B and B2C Web applications each support two application configurations that must be maintained separately:

(16)

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

application.

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

2.2.2 Bookmark Support for B2C E-Commerce

Use

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

Procedure

You enable bookmark support in B2C E-Commerce in the Extended Configuration Management (XCM) application for your B2C Web shop:

Log on to XCM at: http//<servername:port>/b2c/admin/xcm/init.do:

1. Choose Start → General Settings → Customer → B2c → b2cconfig. Set the ReInvokeEnabledparameter to True.

This setting enables the bookmark support independently of session timeouts

2. Choose Start → Components → Customer → shop → <shop component configuration assigned

to your application configuration>.

Enter a shop ID value for the defaultShopID parameter.

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

3. Choose Start → General Settings → Customer → ui → <ui component configuration assigned to

your application configuration>.

(17)

Result

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

2.2.3 XCM Settings for Transaction Maintenance

Use

You need to enable certain parameters in Extended Configuration Management (XCM) for SAP E-Commerce to adapt transaction maintenance to your own needs.

Procedure

1. Log on to Extended Configuration Management (XCM) at http://<servername:port>/<b2c or b2b>/admin/xcm/init.do.

2. Navigate to Start → Components → Customer → basket → <the basket component configuration assigned to your application configuration> and adjust the following parameters:

Parameter Description

lineItemIncrement This parameter defines the increment of line item numbers. The default setting is 10. So line item numbers will therefore 10, 20, 30, and so on.

If you change the value to 100, the line item numbers will be 100, 200, 300, and so on.

This parameter is only relevant if the base configuration of your component configuration is “javabasket”.

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

• Using cookies if the user was not logged on when maintaining the shopping basket.

• Via User logon ID if the user was logged on the Web shop when maintaining the shopping basket.

This parameter is only relevant for a B2C Web shop scenario.

Enabling this functionality may increase the performance hardware requirements.

usedatabaseTemplate Choose True to enable the use of Order templates in ERP

E-Commerce. In addition you have to enable the use of order

(18)

Parameter Description

made order templates will be saved to and read from the SAP Web AS Java 7.00 server.

The XCM setting is not necessary in CRM E-Commerce as there the order templates are written to the CRM database.

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

The database integration parameters can be found at Server → JDBC Connector.

The settings relevant to your application load can be found at Resources → Data Sources →

SAP<SID>DB Additional.

The following parameters can be adjusted: MaximumConnections

Defines how many sessions can access the database in parallel. Maximum Time to Wait for Connections

Defines how many seconds the SAP Web AS Java 7.00 session waits for a database connection before timeout.

3. Log on to Extended Configuration Management (XCM) at http://<servername:port>/<b2c or b2b>/admin/xcm/init.do.

4. Navigate to Start → Components → Customer → basket → <the ui component configuration assigned to your application configuration> and adjust the following parameter:

initial.newpos

This parameter defines how many empty items are initially displayed for a new document and after every refresh.

2.2.4 Web Application Specific Parameters

Use

After you have deployed the web application you need to configure your application. For this application configuration you have to maintain different parameters in Extended Configuration Management (XCM). These parameters define how the deployed web application (e.g. B2B) specifically runs at the customer if the customer specific application configuration that stores the parameter values is used in the Web Shop URL.

(19)

For more information about installation of web components and the XCM tool, see the following documentation in SAP Service Marketplace under the address service.sap.com .

Java Components for E-Selling and Channel Management Installation Guide Web Application Installation Guide

You can access XCM via the following URL:

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

The following tables give an overview on some important configuration parameters. For more information about the parameter settings, see the documentation in XCM.

Secure Socket Layer (SSL)

If you use SSL you have to specify the HTTP and HTTPS port for each application participating in the secure communication.

Settings for SSL in XCM

Parameter Description Location in XCM http.port.core When using HTTPS you have to

specify the HTTP port here. General Settings → Customer → <application name> (for example: b2b)

https.port.core When using HTTPS you have to

specify the HTTPS port here General Settings → Customer → <application name> (for example: b2b)

The protocol between the web server and the SAP J2EE Engine is HTTP, the application is never accessed using HTTPS. That means, if you have the infrastructure Web Browser → HTTPS → Web Server → HTTP → J2EE Engine you need to start the application using the additional request parameter secure, for example “https://host:port/b2b/b2b/init.do?secure=true“.

Controlling the Look & Feel of the Web Application (Mime Objects)

The following parameters control the mime object (pictures, cascading style sheets, etc.) responsible for the look& feel of the web application.

Parameter Description Location in XCM theme.core Themes enable you to manage different

records of mime objects. The parameter specified here determines which record is to be used.

Components → Customer → ui

mimes.core URL to mimes if placed on an external

web server Components → Customer → ui

(20)

Relogin URL in case of Web Application Error

Parameter Description Location in XCM reloginurl.core URL for logging on to the application

after the session is lost. General Settings → Customer → <application name> (for example: b2b)

Multimedia Objects in Web Catalog

Parameter Description Location in XCM imageserver This URL describes the server directory

to which images from the R/3 system are published.

Components → Customer →

webcatalog

Connection Parameters to SAP system

You configure the connection parameters in XCM under Components → Customer → jco.

When you create a new connection parameter configuration you can select whether you want to connect using a message server or directly to the application server host by selecting the Base Configuration 'group_connect' or 'server_connect'.

Showing Java Stacktrace in case of Application Error

Showing a stacktrace can be helpful when testing the application.

Parameter Description Location in XCM Showstacktrace.isacore If set to ‘true’ a stacktrace is shown if an

application error occurs.

For security reasons, the parameter must be set to ‘false’ in a productive

environment.

Components → Customer → ui

2.2.5 Administration

of

Language and Country Settings

Language Settings

The language that is used within the application can be set as follows:

In Extended Configuration Management (XCM), when you specify the connection parameters under

Components → Customer → jco.

(21)

In XCM, you can set the language parameter in the ui component under Components → Customer → ui.

This parameter overwrites the value specified in the jco component. You can use the languagerequest parameter within the URL.

To set the language to ‘German’, the URL with language request parameter is: http://<host>:<port>/b2b/b2b/init.do?language=DE

The URL parameter overwrites the language parameter specified in the XCM components.

Within the shop list only those shops are displayed, which are maintained for the language specified in the URL or in XCM. When specifying a logon language also make sure that it corresponds to the language of the catalog variant assigned to the Web shop.

Country settings

The country of the Web shop you selected is used. The language is used to define the locale, which is used to control data and currency fields.

2.2.6 Tax Determination using the IPC in ERP E-Commerce

Use

You can now configure your system to enable VAT determination in the ERP E-Commerce B2B and B2C Web shops using the IPC. This means you can determine whether gross or net values are displayed to your customers in the catalog.

Procedure

The standard SAP delivery is for net values. If you want to show gross values, in other words display VAT for products, you need to make changes in the backendobject-config file.

1. Open the backendobject-config file.

2. Navigate to the section PriceCalculatorR3IPC. 3. Select the parameter priceTypes.

4. Set the value to grossValue (SAP delivers the value as netValue).

5.

Save your changes.

(22)

2.2.7 Material

Number Format Conversion

Use

You can set different formats for material numbers. This means that you can have one main format and then different variations on it to use in your Web shop, for example to simplify the format for customers to enter in the shop

.

Procedure

You define material number formats in your backed ERP system.

1. In Customizing select Logistics - General → Material Master → Basic Settings → Define Output

Format of Material Numbers.

2. Define the length of the material numbers and, if required, a material number template. 3. Specify the form in which the numbers should be stored.

4. Specify whether the numbers should contain leading zeroes.

For more information, see the documentation fort he Customizing activity.

2.2.8 Delivery

Priority

Field Configuration

Use

You can no maintain a delivery priority in the shopping basket in the B2B and B2C Web shops. The delivery priority field is available at header and item level in the Web shop order. The delivery priority enables customers to signal to you how urgent the delivery is.

Procedure

You enable the delivery priority field in Extended Configuration Management (XCM) for your B2B and B2C applications.

1. Log on to XCM at http://<server>:<port>/<b2b or b2c>/admin/xcm/init.do. 2. Select Start → General → Components and select the application configuration.

3. Enable the following UI parameters: configinfo.order.view

Enables the delivery priority in the shopping basket.

configinfo.orderdetail.view

(23)

2.3 Administrating the Web Application

2.3.1 Administration

of the Web Application

If you want to access the administration area, you must specify the user and a password. The default logon data is:

User Administrator Password No password necessary

You have log on authorization with the role isaadmin. Only users who have been assigned this role can access the area with the URL /admin/*. The administration of users and their authorizations is carried out using the administration console of the SAP Web AS Java 7.00 server.

Quick start to change the administrator password:

1. Start the administrator console of the SAP Web AS Java 7.00 server. 2. Connect to the SAP Web AS Java 7.00 server.

3. Choose the security service of the server. 4. Choose the runtime panel.

5. Choose the User Management panel. 6. Change the password of the administrator.

You can find further information on the security settings in the SAP Web As Java 7.00 server documentation.

Make sure that the pages in the administration area can only be accessed by experts and are not available to end users.

You can use the following URLs to access the administration pages of the SAP E-Commerce Web applications, to reset caches for example:

Business-to-Business SAP E-Commerce:

http://<Web-Server>/b2b/admin/index.jsp

Business-to-Consumer SAP E-Commerce:

http://<Web-Server>/b2c/admin/index.jsp

<Web-Server>: Name of your Web server

Make sure that you protect the URLs mentioned above before you access the Web. The following links are available:

Catalog Cache Statistics

System Cache Statistics

Java Connector Statistics

(24)

2.3.2 Catalog Cache Statistics

On this page you can check the parameters of the cache that is created for the catalogs. The following times are displayed on the top half of the page:

Configured expiration time

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

See Cache Administration of Product Catalogs.

Configured removal time

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

See Cache Administration of Product Catalogs. This specification does not have to be made if no

timeframe was specified there.

Next check of remaining life time

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

Information about the individually buffered catalogs is displayed in the table on the lower half of the page. The table columns have the following meaning:

Key Key, under which the catalog is managed in the cache. Catalog Guid Unique indicator of the catalog (name, variant).

Time Stamp Time stamp that specifies when the catalog was last accessed. Remaining life time Time specification that shows when the catalog was removed from the

cache, if it was not accessed again in the meantime. The check of this time takes place hourly. It is therefore possible that the time specification can be negative.

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

2.3.3 System Cache Statistics

This page gives you an overview of system caches. The table columns mean the following:

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

Num Objects Specifies how many objects are currently stored in the cache. Hits Describes the number of successful read attempts from the cache.

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

Description Description of the cache.

(25)

The following caches are currently available:

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

r3cust Used to temporarily save the customizing that is read from the SAP R/3 backend system. Only relevant for ERP E-Commerce..

r3formatters Used to temporarily save the locale and currency-dependent formattings for the date and currency conversion. Only relevant for ERP E-Commerce.

2.3.4 Java Connector Statistics

The page gives information about Connector Management to the SAP System, which takes place via the SAP Java Connector.

The page is divided into the following areas:

Java Connector (JCo)

Version of the SAP Java Connector.

JCo Pool Statistics

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

pool name Name of the connection pool

max pool size The maximum number of connections to the SAP System that are required per pool up to that point in time

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

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

con states The status of connections that are currently available in the pool

The possible statuses of a connection are: CONNECTED

Connection is in the pool and is available for use. DISCONNECTED

Connection is in the pool, but cannot be used. This situation should not occur in a pool. USED

Connection from the pool is in use. BUSY

(26)

A connection can have one or more of these statuses. For example, the state CONNECTED USED

BUSY means that a connection was issued from the pool, and that a communication is currently taking

place with the SAP System via this connection.

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

JCo Cache Statistics

This area gives information about the function module cache in the Enterprise Application Integration (EAI) layer.

The following specifications are made: Default time to live [min]

The maximum time in minutes that remain for a function module in the cache. Default idle time [min]

The maximum time in minutes that remain for a function module in the cache, if it is not accessed.

The following table gives information about the function modules that are in the cache:

Key (Function Module) The name of the cached function module

Hits Number of times the function module has been accessed Last Access Time Time when the function module was last accessed

Expiration Time Time when the function module will be removed from the cache, if it

is not accessed

clear Link that removes the function module from the cache

2.3.5 Web Application Specific Parameters

See chapter 2.2.4.

2.4 Logging Web Application

Logging in ERP E-Commerce Applications

Use

You need to set up logging within your ERP E-Commerce applications so that you can trace administration issues. You can display and download log files and trace browser sessions.

(27)

The ERP Java components use the standard logging and tracing from the SAP Web AS Java 7.00 server. The system writes logging and tracing messages into the central log files of the SAP Web AS Java 7.00 server. You can use the Log Viewer, which is automatically installed with the SAP Web AS Java 7.00 server, to view the logs and trace files. You can change trace settings for specific locations and categories.

The following table details the most important location in ERP E-Commerce:

Location Description

com.sap.isa Root location for ERP E-Commerce E-Selling applications.

Default severity is set to ERROR.

The following table list categories used in CRM E-Commerce:

Category Description

/Applications/Common/Security Parts of E-Commerce dealing with security. /Applications/UserInterface User Interface Layer (Struts Actions)

/Applications/BusinessLogic Most of the Java-based E-Commerce coding

If certain categories are not pre-configured in the LogConfigurator Service in the Visual Administrator you need to add them manually. For more information, see the Operations Guide on the SAP Service

Marketplace

.

2.5 Connectivity

Connectivity Between IPC and ERP E-Commerce

Use

You set up the SAP Internet Pricing and Configurator (IPC) with your ERP E-Commerce application to enable the use of configurable products in your Web shop and the use of customer-specific pricing in the product catalog.

Depending on the release version of your backend system, you need to carry out different configuration steps to set up connectivity between the IPC and your ERP E-Commerce application.

Release Version Configuration Information

ERP 2005 See Configuring IPC and ERP E-Commerce for

mySAP ERP 2005.

ERP 2004 and lower R/3 release See Configuring IPC and ERP E-Commerce for

mySAP ERP 2004 and Lower Releases.

(28)

Configuring IPC and ERP E-Commerce for mySAP ERP 2005

Use

You set up the SAP Internet Pricing and Configurator (IPC) 7.0 with your ERP E-Commerce application to enable the use of configurable products in your Web shop and the use of customer-specific pricing in the product catalog.

If you are using SAP ERP 2005 release as a backend system you need to carry out the customizing activities described in this document to set up IPC/ERP E-Commerce connectivity.

Prerequisites

You are using mySAP ERP 2005 as your backend ERP system.

The IPC is a component which is automatically installed with the ERP deployment.

Procedure

If you are using ERP 2005 as a backend system for your ERP Commerce application, the ERP E-Commerce application will connect to IPC 7.0 using the JCO connection data which you define in Extended Configuration Management (XCM). You maintain this data as follows:

1. Log on to Extended Configuration Management (XCM) for your Web shop at: http://<servername:port>/<b2c or b2b>/admin/xcm/init.do.

2. Navigate to Start → Application Configurations→ Customer → <the application configuration you wish to use>.

3. In the jcodata parameter field choose the value “select to create component configuration” and then select the jco button.

4. The system displays the component configuration for the JCO connection data. Fill in the values for the parameters in this component and Save your configuration.

Result

The JCO connection data is maintained for your ERP E-Commerce application. The ERP E-Commerce application will connect to the IPC 7.0 using this data.

Configuring IPC and ERP E-Commerce for mySAP ERP 2004 and Lower Releases

Use

You set up the SAP Internet Pricing and Configurator (IPC) 7.0 with your ERP E-Commerce application to enable the use of configurable products in your Web shop and the use of customer-specific pricing in the product catalog.

(29)

If you are using a SAP ERP 2004 release or lower as a backend system you need to carry out the customizing activities described in this document to set up IPC/ERP E-Commerce connectivity.

Prerequisites

You are using one of the following ERP backend releases: o SAP R/3 4.6c

o SAP R/3 Enterprise o mySAP ERP 2004

As CRM 5.0 the IPC is a component in the Application Platform (AP), and a switch in technology has been made to the SAP Virtual Machine Container (VMC), part of the SAP Web AS 7.00 server and SAP NetWeaver 2004s. Therefor yu must have installed the following:

o You have installed the SAP NetWeaver 2004s Application Server ABAP. For more information, see the SAP NetWeaver 2004s <Technology> on Operating

System>:<Database> installation guide on the SAP Service Marketplace at

service.sap.com/crm-inst.

o You have enabled the Virtual Machine Container (VMC), as described in SAP Note 854170.

o

You have installed the SAP Application Platform (SAP AP) Addon, as described in SAP Note 848412.

Procedure

To connect to the IPC from an ERP E-Commerce application, when you are using an ERP Release of ERP 2004 or lower, you must carry out the following customizing activities to configure the IPC.

Initialize user exit customizing

1. Carry out the steps in SAP Note 878865 to initialize user exit customizing.

2. Extract the Java classes for the compilation of user exits or variant functions from the AP 7.00 database using path: /SAPCND/UE_JAVA_DOWNLOAD.

3. Deploy the user defined classes using SAP Note 870201.

Configure the download of IPC Knowledge Bases

1. Register the Event Handler in ERP

To enable a delta download of knowledge bases for the Configuration Engine in AP you have to register an event handler. In table TBE31 register the event handler and indicate it as follows:

EVENT LAND APPLK FUNCT

00550002 BC-MID CRS_SCE_COLLECT_DATA_CHANGE

2. Register a New Consumer in ERP

To enable the download of knowledge bases you have to specify a consumer in ERP. A consumer is the system which will receive the IPC data.

(30)

CONSUMER AKTIV TEXT Q_PREFIX

IPC X IPC IPC b. In the table CRMRFCPAR specify the AP system addresses, type, and download handling: CONSUMER OBJNAME DOWNLOAD RFCDEST RFC IN

QUE

BAPINAME USE IN Q IPC SCE I <RFCDEST> <INQUE> AP_SCE_INIT X

IPC SCE D <RFCDEST> <INQUE> AP_SCE_DELT X Download Types:

I – to initialize download of all given knowledge bases of the Configuration Engine. Existing knowledge bases will be overwritten.

D – to initialize delta download of knowledge bases of the Configuration Engine. Replace <RFCDEST> with the appropriate RFC destinations of the AP system.

When creating the RFC destinations make sure you grant full authorizations in the S_RFC object to AP SU01 connection user.

Replace <INQUE> with the appropriate AP system buffer names.

Enter X in the USE IN Q field if you are using buffers.

3. Specify RFC Destinations in the AP system

To enable the initial download of the knowledge databases you must specify the ERP systems which will deliver the data. You maintain the RFC destinations for these systems in your AP system and name them as follows:

IPC_REMOTE_DB_CONNECTION_<CLIENT>. Replace <CLIENT> with the AP system client number, for example, 003.

When creating the RFC destination, remember to grant the following authorizations to the ERP SU01 connection user:

Assign full authorizations in object S_RFC to the ERP SU01 user

Assign authorizations (ACTVT=3) for the pricing customizing and master data tables using

authorization object S_TABU_DIS. Since the pricing attributes can vary you should either grant full display authorizations for the S_TABU_DIS object, or perform an authorization trace to determine the appropriate values.

If you want to carry out a more advanced authorization check, you can use the BAdI

EXTRAC_DATA_IPC. Without customer-specific implementation, the standard default setting gives access to all tables. You can limit user access to particular tables using the method

CHECK_TABLE_ACCESS. Set the parameter EV_ACCESS_ALLOWED to SPACE for all tables for which access should be denied.

4. Initialize Database in AP

You have to carry out an initial download of all given knowledge bases to initialize the database in the AP system. Once this is done you can run the Configuration Engine in AP.

(31)

To carry out the download run the report CFG_AP_INITIALISE_DB. This report will initialize the configuration database in AP.

The initial download will overwrite existing knowledge bases.

If errors occur during data storage to the database, the system will generate an error message and send it to the message log.

5. Set up Specific Knowledge Base Downloads

You may need to download specific knowledge bases on request. This knowledge bases will contain specific data that you need for running the Configuration Engine in AP. Run the report

CFG_AP_REQUEST_DB to download specific appropriate knowledge bases

Connect ERP E-Commerce to the AP system

You have to maintain JCO connection data to enable the connection between ERP E-Commerce and the IPC component which is installed on the AP system. You maintain this connection in Extended

Configuration Management (XCM) for your Web shop. Proceed as follows: 1. Log on to Extended Configuration Management (XCM) for your Web shop at: 2. http://<servername:port>/<b2c or b2b>/admin/xcm/init.do.

3. Navigate to Start → Application Configurations→ Customer → <the application configuration you wish to use>.

4. Choose Advanced Settings → Display.

5. In the ipcjcodata parameter, select the value “select to create component configuration” and then select the jco button.

6. The system displays the component configuration for the JCO connection data. Fill in the values for the parameters in this component and Save your configuration.

Make sure that the user you maintain in the user parameter in the JCO configuration component has the following authorizations:

Authorization object S_MI_ADMCO : full authorizations

Authorization object S_RFC : For a list of authorizations and how to proceed, see the information for

Scenario C in the SAP Note 412309.

2.6 Configuring User Management in ERP E-Commerce

You can create and manage users for your ERP E-Commerce Web-based applications. A user provides customers and employees with access to Web-based applications, for example the Web shop or the

(32)

Customer Portal, and determines, through the use of authorization roles, which activities and transactions they can carry out within these applications.

To be able to create users for your ERP E-Commerce applications you need to carry out various customizing and configuration activities in the following areas in your backend ERP system and in the Java-based Extended Configuration Management (XCM) applications.

To enable user management you need to carry out the following activities:

Determine ERP E-Commerce SU01 Logon Types

Configure user management in your backend and Java-based applications

Modify authorization roles for the authorization concept

Configure ERP E-Commerce with the SAP NetWeaver Portal

2.6.1 ERP E-Commerce SU01 Logon

Use

When configuring the user type for ERP E-Commerce in Extended Configuration Management (XCM) you have the choice of two logon procedures if you are running an SU01 based logon configuration.

If you are running the Shop Management and Web-based User Management applications, only the logon configuration for SU01 users, and not SU05 users, is available to you.

ERP E-Commerce logon

B2B user types: R3_SU01User, R3_SU01UserContactPerson, R3_SU01UserStandalone

ERP E-Commerce logon via UME

B2B user types: R3_UMESU01User, R3_UMESU01UserContactPerson, R3_UMESU01UserStandalone

The logon configuration determines how users logon to the applications and the steps the system takes to verify users and perform checks on authorizations.

For a full list of all ERP logon user types (SU01 and SU05) for the ERP E-Commerce applications, see Log-On Types for ERP E-Commerce.

ERP E-Commerce SU01 logon

The ERP E-Commerce SU01 logon is technically part of the ERP E-Commerce Web application and has the following characteristics:

It can be used for B2B and B2C Web-based applications Logon using SU01, user IDs, and SSO

Expired/existing password change Switch to SSL before user logs on Logoff function

It can read a Single-Sign-On (SSO) ticket but cannot create an SSO ticket No cookies needed

All configuration is done in the ERP E-Commerce XCM administration tool

ERP E-Commerce SU01 logon via UME

The ERP E-Commerce SU01 logon via UMEis technically part of the SAP Web AS Java 7.0 and runs with the User Management Engine (UME). It has the following characteristics:

(33)

It can only be used for B2B Web-based applications

Support of all UME logon variants (Single sign-on, X.509, JAAS, etc)

Enhanced password functionality (forgotten password, reset, contact administrator) It reads and generates Single-Sign-On (SSO) tickets

Secure Sockets Layer (SSL) switch Logoff function

Cookies needed

Configuration is done in addition to the ERP E-Commerce application configuration.

For more information on installing the ERP E-Commerce SU01 Logon via UME, see SAP Note 805713 and the ERP E-Commerce SU01 logon via UME.

For a full list of all ERP logon user types (SU01 and SU05) for the ERP E-Commerce applications, see

Log-On Types for ERP E-Commerce.

ERP E-Commerce SU01 Logon via UME

Use

The User Management Engine (UME) provides centralized user management for your Web-based applications, and you can configure it to work with user management data from several sources. In ERP E-Commerce you can use the UME logon application with the ERP E-Commerce SU01 logon to enhance your Web-based application logon functionality. A typical reason for combining User Management in ERP E-Commerce with UME is when you are running ERP E-Commerce in the SAP NetWeaver Portal. Integrating UME with your E-Commerce logon procedure ensures that the system carries out the following checks when a user tries to logon to an application:

The system carries out the first check when the user logs on using the user ID and password. The system calls the UME logon application, which checks the user data and creates a single sign-on (SSO) ticket if the check is successful.

The system uses this SSO ticket to perform the second security check, this time within the SAP E-Commerce application the user is trying to access.

Once logged on with the UME logon application, the user can access all SSO-enabled applications using the SSO ticket. To provide SSO functionality you must ensure that the UME and ERP E-Commerce users have the same user IDs.

(34)

To combine User Management for ERP E-Commerce with the UME user base you have to maintain the ERP E-Commerce users and the UME users simultaneously. You can do this in one of the two following ways:

UMEuses the SAP E-Commerce user base in the backend system as its own user base.

This scenario is relatively easy to configure, however in the portal environment it has the consequence that all portal user, not only the ERP E-Commerce users, have to be created and maintained in the backend system. You configure UME to use the ERP E-Commerce user base.

UMEuser base and SAP E-Commerce user base are separate.

This means that you have to synchronize the two user bases. You have to configure the ERP E-Commerce Web-based User Management application by choosing a specific base configuration (b2bWithUME) in the Extended Configuration Management (XCM)application for the User Management tool. In addition, you have to define mappings between the roles for Web shop users and the UME roles.

For detailed installation and configuration of this scenario, see SAP Note 713472.

Procedure

To enable the ERP E-Commerce SU01 logon via UME with UME you need to carry out the following configuration activities:

1. Configure the UME logon application.

For more information on configuring the UME logon module, see the UME Configuration documentation in SAP Solution Manager.

2. To enable UMEset the usertype parameter in Extended Configuration Management (XCM) for Web-based User Management:

Config Guide ECO ERP 50

SAP E-Commerce for

mySAP ERP:

Business Scenario

Configuration Guide

Copyright

Icons

Typographic Conventions

Contents

Important information regarding this document

Harmonized naming for SAP E-Commerce

SAP E-Commerce for mySAP ERP 5.0:

Business Scenario Configuration Guide

1 Purpose



2 Configuration

2.1 ERP E-Commerce System Prerequisites





2.2 Configuring the Web Application

2.2.1 Extended Configuration Management (XCM)

Use

Procedure

Starting XCM

Printable Help

General Settings

:

Multiple Application Configurations

Delivered SAP Configuration

Create a Customer Application Configuration

Configure a Customer Application Configuration

Creating a New Component Configuration

Testing a Component Configuration

Define a Default Application Configuration

Save the Application Configuration

Activating the Application Configuration

Running the Web Application

Uploading and Downloading XCM Settings

Downloading XCM Configurations

Uploading XCM Configurations

Indication of Obsolete XCM Settings

IPC Switch for XCM Configuration of SAP E-Commerce

2.2.2

Bookmark Support for B2C E-Commerce

Use

Procedure

Result

2.2.3 XCM Settings for Transaction Maintenance

Use

Procedure

2.2.4 Web Application Specific Parameters

Use

Secure Socket Layer (SSL)

Controlling the Look & Feel of the Web Application (Mime Objects)

Relogin URL in case of Web Application Error

Multimedia Objects in Web Catalog

Connection Parameters to SAP system

Showing Java Stacktrace in case of Application Error

2.2.5 Administration

of

Language and Country Settings

Language Settings

Country settings

2.2.6 Tax Determination using the IPC in ERP E-Commerce

Use

Procedure

5.

2.2.7 Material

Number Format Conversion

Use

.

Procedure

2.2.8 Delivery

Priority

Field Configuration

Use

Procedure



2.3 Administrating the Web Application

2.3.1 Administration