Sie sind auf Seite 1von 11

SAP Web Channel Experience Management

WCEM 2.0 on ERP Catalog Usage and Related Information

Applicable Releases: SAP WCEM 2.0 Topic Area: Catalog Usage for WCEM 2.0 on ERP backend Business Scenario: WCEM Catalog Usage & Supporting Applications

Version 1.0 May 2012 Contacts:


Janet Tran (janet.tran@sap.com) SAP GTM Customer Solution Adoption Rajesh Ganjur (rajesh.ganjur@sap.com) SAP Americas LOB Consulting

Copyright 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software materials marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP materials 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 material and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National material specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group materials and services are those that are set forth in the express warranty statements accompanying such materials and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the material implementation. While specific material features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (Code) included in this documentation are only examples and are not intended to be used in a material live system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this material are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this material is only to be used by SAPs Support Services and may not be modified or altered in any way.

Document History
Document Version 1.10 1.00 Description << Enter your summary of changes in this version >> First official release of this guide

Typographic Conventions
Type Style Example Text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Icons
Icon Description Caution Note or Important Example Recommendation or Tip

Example text

Example text

<Example text>

EXAMPLE TEXT

Table of Contents
1. 2. 3. 4. Business Scenario............................................................................................................... 1 Background Information ..................................................................................................... 1 Prerequisites ........................................................................................................................ 1 Material Catalog for ERP Backend..................................................................................... 2 4.1 Using MDM Catalog for Material Catalog ..................................................................... 2 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.2 4.2.1 4.2.2 4.3 5. Catalog Requirement & Scenario .................................................................... 2 Catalog Navigation & Usage with WCEM 2.0 .................................................. 2 Catalog Structure with WCEM 2.0 ................................................................... 3 E-Commerce Order Management and MDM Catalog ..................................... 3 MDM Catalog Multimedia Functionality ........................................................ 3 Catalog Requirement & Scenario .................................................................... 4 Ecommerce Order Management and ERP-TREX Catalog.............................. 4

Using ERP-TREX Catalog for Material Catalog ........................................................... 4

MDM and ERP-TREX Catalog ..................................................................................... 5

Key Feature Comparison .................................................................................................... 5

1. Business Scenario
Evaluate options to use Material Catalog for WCEM 2.0 with ERP back-end.

2. Background Information
This document is meant to supplement standard information provided for WCEM 2.0 at http://help.sap.com/wec. Standard support for WCEM 2.0 catalog: 1. ERP Backend can be supported by MDM Catalog OR ERP-TREX Catalog 2. CRM Backend supported by MDM Catalog ONLY 3. A Web Shop equates to a Web Application. Multiple Web Applications can exist within one WCEM system. 4. Web Channel Experience Management will be frequently referred to as WCEM in this document.

3. Prerequisites
WCEM 2.0 on ERP backend Material master data migration from ERP to MDM (only applicable to MDM catalog).

4. Material Catalog for ERP Backend


Customer who implements WCEM on ERP backend has the option to either utilize MDM material OR ERP-TREX material catalog. The decision on which catalog tool to utilize is dependent on the customer requirements and circumstances. In this section, we will detail the requirements and approach for each option.

4.1
...

Using MDM Catalog for Material Catalog

This function allows SAP ERP Material master data to be used by a Web shop. The master data is stored in SAP NetWeaver Master Data Management (SAP NetWeaver MDM) repositories and then assembled into material catalogs. Material catalogs contain Material details, for example, descriptions, images, and pricing information that can be tailored to meet a customer's needs. Note: 1. You cannot use generic Articles with the MDM material catalog when importing data from ERP (only supported for MDM Catalog with CRM backend) 2. Will need to have PI in place to migrate material master data from ERP to MDM. 3. Delta synch is not supported. To sync changes to Material master data in ERP to MDM, need to repeat Initial load. Reload to MDM is executed as Merge & Update thus will not override existing data already available in MDM via previous Load from ERP and/or direct maintenance in MDM. 4. MDM Catalog Area Type - This field is NOT currently utilized by WCEM. Leave blank.

4.1.1

Catalog Requirement & Scenario

Gather catalog customer catalog requirements prior to determining the approach. 1. If your catalog requirement is complex and contains one or more of the following criteria, then you may consider using MDM material catalog: a. High Material volume supported (no maximum cap) b. Multiple sale areas c. Multilanguage d. Multicurrency e. Images (multiple images supported) f. Advanced Search capabilities (Material ID and Description, plus Classification attributes supported out of the box)

4.1.2

Catalog Navigation & Usage with WCEM 2.0

Determine the customers requirement on catalog UI to determine navigation mode. 1. Catalog Navigation Mode a. Area Direct only display materials directly assigned to a catalog node in MDM (via Catalog Area in MDM). b. Area Hierarchy On a parent node, all materials underneath the parent node will be displayed (inherits materials from all child nodes). c. Category Display all materials assigned to the category. Category without any material assignment will NOT be displayed. The # of material count is displayed for each category and is altered by filter selection, search etc.

d. Combined (Area Direct + Category) Display materials directly assigned to a catalog node and also display category underneath each node.

4.1.3

Catalog Structure with WCEM 2.0

Leveraging backend material classification (ERP) to build MDM catalog structure. This is supported via Category Mode Navigation or Combined Mode Navigation. 1. ERP Backend Material Classification a. During material migration process from ERP to MDM, the material classification structure meant to be used as the structuring hierarchy needs to be uploaded into MDM via transaction MDMGX. Specify the root class in the extractor and all subclass will be uploaded as well. Then, upload the materials so they appear as linked to one of the class in the tree (table material taxonomies in MDM). b. MDM catalog does not support materials which are assigned to two different classes. c. Also only Class Type 001 is supported.

4.1.4

E-Commerce Order Management and MDM Catalog

1. Can search for all materials that are in MDM repository. 2. Using List Price Catalog Items Display Catalog items will NOT be displayed in the Web Shop if the corresponding "valid" list prices are NOT available in the MDM repository (via download from ECC). The MDM catalog program logic only supports standard pricing condition tables 004, 005, 073, 304 & 305 to retrieve list prices & integrate with WCEM via Web Channel Builder (WCB). a. If you utilize different standard or custom pricing condition tables, the information will only be partially uploaded. Hence, if you configure WCB to use such a standard table other than the ones supported (i.e. 004, 005, 073, 304 & 305) or a custom condition table, the materials will only be filtered based on the valid flag/date & currency. This is not recommended. Extension: Implement MDM repository + Java API related enhancements to accommodate non-standard pricing condition tables. (Note: This is classified as a customer enhancement.) 3. Using Dynamic Price for Catalog Items Display Dynamic price is used to display customer specific pricing in the catalog. Pricing Engine (formerly IPC) is used to dynamically calculate pricing from ECC backend. However, you still need to upload the list price condition records from ECC into MDM so every product that needs to appear in the shop has a valid price at browsing time. If not, the product will not be displayed, even though IPC has successfully calculated the customer specific price. Download of conditions from ECC to MDM is required for list prices. Extension: Implement MDM Java API enhancement to ignore list price prerequisite. Override the class "ListPriceFilteringManagerImpl" with empty implementation for all public methods. (Note: This is classified as a 'core' modification.)

4.1.5

MDM Catalog Multimedia Functionality

1. MDM WCEM Catalog & Attachments a. Images Supported formats (BMP, GIF, JPG, etc.) i. Default Image supports 1 default image for material overview. ii. Additional Images supports multiple images in addition to the default image iii. Attaching Images Images can be stored directly in MDM repository (Store in MDM option) or via logical link (Link to Original File Only option). When link to original file, 1. After making changes to image while keeping the same image file name, you must go to MDM Data Manager and Reimport the image for the change to take effect.

2. After making changes to image with different file name, you must go to MDM Data Manager and Replace the image to establish the link of the new image file to the material. b. Document Attachments i. Does not support direct attachment of documents in MDM. This can be accomplished via work around using Text HTML (.htm or .html). The HTML file must come from extranet and not intranet (security issues). Also has ability to have a 100% custom html page embedded, this nearly has no limit to the content that can be placed since it supports / inherits whatever the HTML page can support. ii. Document Attachments can be stored in MDM similar to Images however WCEM currently does not support the display of Document Attachments in the Product Details page wherein a JSF enhancement is needed to adjust the layout and enable display.

4.2
...

Using ERP-TREX Catalog for Material Catalog

This function allows SAP ERP Material master data, assembled into SAP ERP material catalogs, to be used by a Web shop. The master data is replicated from SAP ERP to SAP TREX and stored within an index file. The Text Retrieval and Information Extraction (also referred to as Search and Classification) engine, uses the Indexed Catalog files to enable the Web Shop to search for and retrieve material details, for example material ID and description plus list pricing information at the Material level out-of-the-box. This can be further tailored to meet Customers needs via enhancements. In ECC catalog, the variant is defined as a unique combination of language & currency and upon replication, stored in TREX as independent index files. Note: 1. You cannot use generic Articles with the ERP-TREX material catalog. 2. Delta replication of ERP Catalog to TREX is not supported; Initial replication will have to be re-run as needed to sync updates 3. Transaction ISA_CAT_REPLICATION to replicate ERP Catalog to TREX only supports one Variant at a time

4.2.1

Catalog Requirement & Scenario

1. If your catalog requirement is basic and contains one or more of the following criteria, then you may consider using ERP-TREX material catalog: a. Single Sale Area at Catalog Header relevant for Web Shop assignment (however Materials included in the Catalog can be across multiple Divisions). b. High Material volume not supported (<100,000 materials limit recommended) c. Single language per catalog variant d. Single currency per catalog variant e. Images (2 images per material) f. Basic Search capability (Material ID and Description supported out of the box)

4.2.2

Ecommerce Order Management and ERP-TREX Catalog

1. Can search for all materials that are in TREX index. 2. Only Area based navigation mode is supported for ERP-TREX Catalog out-of-the-box. 3. Documents can be attached to the ERP Catalog object in ECC backend at the Material level; but the constraint remains on the WCEM side, where the display of those Attachments is currently not supported in the Product Details page (WCEM 2.0).

4.3

MDM and ERP-TREX Catalog

1. Customer specific pricing in Catalog after user logon (B2B scenario) Need to enable Dynamic Pricing in Web Channel Builder (module Catalog) and enable utilization of IPC as a prerequisite. 2. Shopping Cart Quick Order Entry It is possible for web shop customers to enter Material ID which are NOT in the material catalog but available in the ERP backend: a. Backend cart (meant for B2B scenario): As long as the Material exists in ERP backend, it can be entered in the Shopping Cart. i. The Material does NOT have to exist in MDM repository or be assigned to MDM Catalog. ii. The Material does NOT have to exist in the ERP-TREX Catalog. b. Java cart (meant for B2C scenario): The Material exists in ERP backend, AND i. It also has to exist in MDM repository (but not required to be assigned to the MDM Catalog). ii. It has to exist in the ERP-TREX Catalog. Alternate options to restrict material entry: iii. Use listing/exclusion on the ECC Backend to make sure, that such a material does not make it in to the order. iv. Introduce a check against the MDM Catalog or ERP-TREX Catalog via enhancement. v. Disable quick order entry feature via enhancement. 3. Irrespective of the scenario used (MDM Catalog or ERP-TREX Catalog), a Customer enhancement would be needed to enable the display of attachments in the Product Details page of the WCEM 2.0 Catalog.

5. Key Feature Comparison


For more detailed information, please see related product master, installation, configuration guides, SAP Notes, and SAP online help.

MDM Catalog MDM is a composite Product Information Management (PIM) application which includes definition, maintenance and hosting of the Web Catalog. Only applicable to WCEM solution Supports CRM and ECC backend deployment options for WCEM solution. MDM Catalog does not have a Variant concept. MDM server architecture by default is highly scalable as per the recommended standard deployment model. MDM Catalog supports multiple Navigation modes out-of-the-box. No restriction on Sales Area

ERP-TREX Catalog TREX is an Index Management System (IMS) limited to just hosting of the Catalog, after it is defined and maintained in the backend System (ECC). Applicable to both WC Enablement and WCEM solutions. Supports ONLY ECC backend deployment option for WCEM solution. ERP-TREX Catalog is primarily based on a Variant concept. TREX server architecture is limited in terms of scalability (specifically in the context of the ERPTREX Catalog integration scenario for WCEM). ERP-TREX Catalog only supports Area based navigation out-of-the-box. Single Sales Area at Catalog Header

No restriction on Language / Currency Single Catalog model sufficient to meet most Customer scenarios.

Separate Variant required for each unique combination of Language & Currency. Multiple Catalog Variants needed to meet most Customer scenarios (where each Variant is a separate Index on TREX). Potentially Multiple Catalogs as well when dealing with more than one Sales Area. Valid List Price is NOT a mandatory requirement

Valid List Price is a mandatory requirement that governs the display or non-display of Materials in the Web Shop. Multiple Catalogs in MDM supported but only one Catalog can be assigned within a Web Shop. Material master (mandatory), Classification (optional) and List Price Condition data (mandatory in case List price is used instead of Customerspecific price) has to be downloaded from ECC to MDM via PI. Supports one default image and multiple additional images per material (when an image is loaded, an equivalent thumbnail is generated and stored in addition to the original image). Catalog is modeled and resides on MDM (no additional replication) No restrictions on Catalog volume. Additional hardware for MDM / PI. Initial material download from ERP to MDM. Delta download is not supported. Rerun initial download to support material changes as necessary. If Customer-specific pricing is needed to be displayed in the Catalog (post login B2B), then dynamic pricing option has to be enabled which requires use of IPC as a pre-requisite. Supports the assignment of 1 Million Materials to a single Catalog Node and subsequent display in WCEM Web Shop. Catalog Staging concept is not supported. Customer-specific Views are not supported in MDM Catalog. Display of attachments (documents) in the Catalog Product Details page is not supported out-of-the-box

Multiple Catalogs in ERP / TREX supported but only one Catalog Variant can be assigned within a Web Shop. No data downloads.

Supports one thumbnail and one large image per material (loaded separately).

Catalog is first modeled in ECC and then replicated to TREX. Catalog volume more than 100K not recommended. Additional hardware for TREX. TREX hardware requirements could be lesser compared to MDM. Initial catalog replication from ERP to TREX. Delta replication is not supported. Rerun initial replication to support catalog changes as necessary. If Customer-specific pricing is needed to be displayed in the Catalog (post login B2B), then dynamic pricing option has to be enabled which requires use of IPC as a pre-requisite. Supports the assignment of 9,999 Materials to a single Catalog Node and subsequent display in WCEM Web Shop. Catalog Staging concept is not supported. Customer-specific Views are not supported in ERPTREX Catalog. Display of attachments (documents) in the Catalog Product Details page is not supported out-of-the-box