rapid data load for hybris Marketing April 2015 English rapid data load for hybris Marketing: Software and Delivery Requirements SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany Document Revisions 0 1 2 Date
Copyright 2015 SE or an affiliate company. 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 SE or an affiliate company. and other products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SE (or an affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SE or an affiliate company for informational purposes only, without representation or warranty of any kind, and SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SE or affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. SE Public Page 2 of 10
Icons Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice 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 EXAMPLE TEXT Example text Emphasized words or phrases in body text, titles of graphics and tables. 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. 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 <Example text> Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SE Public Page 3 of 10
Table of Contents 1 Purpose of the Document... 5 2 General Project Prerequisites... 5 3 Technical Requirements... 5 3.1 Software Product Versions... 6 3.1 Additionally required for address cleansing and geocode load... 6 3.2 Notes... 7 3.3 Solution Manager and Solution Manager Content Add-On... 8 3.4 Best Practices Solution Builder and Activation Content Add-On... 9 3.5 Active Business Functions... 9 3.6 System Landscape... 9 3.7 Connectivity... 10 3.8 Authorizations... 10 SE Public Page 4 of 10
1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software products and versions match the customer situation Check that all prerequisites for a customer implementation are in place Check that correct content, tools and skills are in place before the project starts The document lists different kinds of requirements on package level if they are valid for all scope items included in the package. For requirements valid for certain scope items only, these scope items are mentioned. The document contains pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the configuration guides. 2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start. Prerequisite Kick off and workshop dates, location and attendees agreed team allocated with correct skills and training in place Project sponsors and stakeholder identified Hardware fully commissioned Software licenses in place Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports User interfaces agreed e.g. GUI, Netweaver Business Client or Portal Remote access is in place for consultants and Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether Best Practices Solution Builder will be used to activate content. Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed Responsibility 3 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided. SE Public Page 5 of 10
3.1 Software Product Versions The following software products and versions (technical names) are required: Product Product Version Components Comments Relevance HYBRIS MARKETING HYBRIS MARKETING 1.1 (1502) CUSTOMER ENGAGEMENT INTELL 1.1 is required All Scope Items DATA SERVICES DATA SERVICES 4.2 SP3 DATA SERVICES SBOP INFORMATION PLAT SVCS 4.1 SP4 PL3 SBOP INFORMATION PLAT SVCS 4.1 to install if there is no existing SBOP BI Platform installation All Scope Items HANA PLATFORM EDITION HANA PLATFORM EDITION 1.0 SPS8 rev.85 or SPS9 rev.93 Required to run the hybris Marketing solution All Scope Items NETWEAVER NETWEAVER 7.4 SP9 NW 7.4 SP9 necessary to run the hybris Marketing solution All Scope Items 3.1 Additionally required for address cleansing and geocode load To run the geocode solution and the social media solution you also need to install address directories. Address Directories are used in various Data Quality offerings to ensure the most current address information. To determine geocodes by an address, you need to have the GEO directories by NAVTEQ or TOMTOM (2012 or later). If you are using the geocode solution and there is no GEO directory installed the related Data Services will run on an error. See also the notes 1308086 and1483331. Address directories can be found on the Service Marketplace. Go to https://support.sap.com/swdc Software Downloads Installation and Upgrades Browse our download catalog Analytics Solutions Address Directories & Reference Data The table lists some exemplary required address directories. Dependent on the different address countries it might be necessary to install other or additional address directories. Product Product Version Component Comments ADDR DIR ALL WORLD ADDR DIR ALL WORLD 4.X SBOP ADDR DIR ALL WORLD BusinessObjects address directories 4.X, global edition ADDR DIR ADDR US SBOP ADDR DIR US BusinessObjects SE Public Page 6 of 10
Product Product Version Component Comments US 2009 - CURRENT address directory, U.S. version GEO DIR US - NAVTEQ GEO DIR GERMANY - NAVTEQ ADDR GEO US - TOMTOM GEO DIR US (PARC) - TOMTOM GEO DIR US- NAVTEQ 4.X GEO DIR DEU-NAVTEQ 4.X ADDR GEO US - TOMTOM GEO DIR US (PARC)- TOMTOM4X SBOP GEO DIR US - NAVTEQ SBOP GEO DIR GERMANY - NAVTEQ SBOP ADDR GEO US - TOMTOM GEO DIR US (PARC) - TOMTOM BusinessObjects geocoding for United States by NAVTEQ BusinessObjects geocoding for Germany 4.X by NAVTEQ BusinessObjects geographical address directory, monthly version for TomTom 1.0 BusinessObjects geocoding for United States (parcel point) 4.X by TomTom 3.2 Notes The following Notes need to be considered: Note No Content Comments Relevance 2078075 This Note contains information for implementing the rapid data load for hybris Marketing. 2082067 This Note contains FAQs to easy problem diagnostics for social media load of rapid data load for hybris Marketing 77430 Customizing: Current settings Before you start implementing the package, check the latest versions of this Note. Before creating a ticket, read the note carefully and check your settings Note with information to mark customizing tables and activities as current settings, for which you don t need to create transport requests in Productive systems. All Scope Items DI6 Load social media data DJ6 Implement Social Data Harvesting Connector DI6 Load social media data DJ6 Implement Social Data Harvesting Connector Might be needed if search terms should not be stored as customizing SE Public Page 7 of 10
Note No Content Comments Relevance 1951554 Unable to locate Cleansing Package download for Data Services 4.2 2058705 Issue with assigning sentiments to entities With version 4.2 of Data Services and Information Steward, the Cleansing Package is no longer a separate download. The Cleansing Package is now part of the Data Services and Information Steward install packages. The Cleansing Package for 4.1 is not used with the 4.2 versions of the software. The variant created for the report "SMI_SENTIMENT_ASSIGNMENT" is not visible during the execution of the transaction 'SOMI_SENTI_ASSIGN' DH4 Load geocodes DI0 Load interactions DJ4 Load emails DI6 Load social media data DI6 Load Social media data 3.3 Solution Manager and Solution Manager Content Add-On For the implementation of the solution package, Solution Manager is recommended. Product Product Version Comments Solution Manager Solution Manager 7.0 Enhancement Package 1 SP18 or higher Or Solution Manager 7.1 SP01 or higher Or Solution Manager 7.1 on HANA (ST 712) SP00 or higher If using Solution Manager 7.0 with SP below 24, see Note 1579267. For rapid-deployment solutions, implementation content is available in Solution Manager templates. The Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from Software Download Center on Service Marketplace at service.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see Note 1726649 and Note 1686668 respectively. In the ST-RDS 100 content add-on, access the template in the following way: If you have Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below. If you have Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below. SE Public Page 8 of 10
Template ID and Template Name Solution Package Name(s) RDS_DAT_LOAD_CEI11V3 - rapid data load for hybris Marketing_V3 rapid data load for hybris Marketing_V3 3.4 Best Practices Solution Builder and Activation Content Add-On For tool-supported, automated activation of the solution package, Best Practices solution builder is recommended. Product Product Version Comments Best Practices solution builder BP-SOLBLD 70Vx Always use the latest available version as outlined in Note 1301301. Add-on for the implementation tool (only necessary to be implemented in a system where content activation shall be done using the Solution Builder (i.e. Sandbox or Development System). 3.5 Active Business Functions Functionality in this solution package requires certain business functions to be active in the landscape. These business functions need to be activated: Product Business Function Configuration or Data required Relevance NETWEAVER FND_SOMI_DS Switch for Social Data harvesting from DataSift DJ6 DI6, DJ4 (optional) NETWEAVER FND_SOMI_CM Social Consent Management DJ6, DI6, DJ4 (optional) 3.6 System Landscape The standard data replication from a Business Suite system ( ERP 6.00 and/or CRM 7.01) to the hybris Marketing solution is done via Landscape Transformation ( LT Replicator). The non- data which will be loaded into hybris marketing is extracted by Data Services into a staging area on HANA. Within Data Services the data will be mapped, cleansed, validated and loaded into the HANA database tables used by hybris Marketing. SE Public Page 9 of 10
hybris Marketing 1.1 (1502) ERP 6.00 LT 2.0 Standard (side-by side scenario) NetWeaver 7.40 AS ABAP SP9 CRM 7.01 Social Media Data provider DATASIFT rapid deployment solution SCI HANA 1.0 SPS08 CVI AI ADT _CUAN_CRM PRI Non- CRM Non- ERP Interactions Emails Survey data Data Services 4.2 SP3 Social Data Harvesting Connector RDS Content Data Quality Management _CUAN_ERP _CUAN Social Intelligence 2014 AG or an affiliate company. All rights reserved. 3.7 Connectivity Dependent on the hybris Marketing installation there might be systems to connect to hybris Marketing. 3.8 Authorizations The authorizations required are dependent on the chosen scope items and are listed and described in the related configuration guides. SE Public Page 10 of 10