SAP POS DM and SAP Customer Activity Repository POS Transaction Data Migration Guide Target Audience

■ Consultants

Internal Document version 1.03 – 07/07/2014

© Copyright 2014 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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 and Java are registered trademarks of Oracle and/or its affiliates. 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.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri and Xcode are trademarks or registered trademark of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings, LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. The content of this documentation is not part of SAP product documentation. By using this guide, YOU AGREE that unless expressly stated otherwise in your agreements with SAP, the content of such site is not part of SAP product documentation and that you may not infer any product documentation claims against SAP based on this information. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. gSOAP Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Neurottstrasse 16 69190 Walldorf, Germany (hereinafter: SAP) and you (hereinafter: Customer) a) Subject Matter of the Agreement A) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee. B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged:

Copyright 2014 SAP AG E) The Customer may distribute original or modified STLport sources, provided that: o The conditions indicated in the above permissions notice are met; o The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Coypright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies.

Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. b) Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included. All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. c) Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. d) Limited Liability A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software. C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000. E) The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP. 4. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

Typographic Conventions Type Style Description

Example Text 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

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text 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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons Icon Meaning

Caution Example Note Recommendation Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

July 2014 7

Contents

Document History ..................................................................... 9 Why is POS Transaction Data Migration Necessary? .......... 10

2.1 SAP Notes for the Migration ........................................................... 11 2.2 Standard SAP Data Provisioning/Replication Mechanisms ........ 11 2.2.1Ineffectiveness of Standard Data Provisioning for POS Transaction Data Migration ..................................................................... 13 2.3 Supported Migration Paths ............................................................. 14 2.4 Out of Scope ..................................................................................... 15

Planning Your Migration Project............................................ 16 3.1 Prerequisites .................................................................................... 16 3.2 Assumptions .................................................................................... 16

Migration Paths and Options ................................................. 17 4.1 SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA ..... 17 4.1.1Local Migration ................................................................................. 17 4.1.2Remote Migration ............................................................................. 19 4.2 SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP Customer Activity Repository 1.0........................................................... 20 4.2.1Remote Migration ............................................................................. 20 4.3 SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA .................................................................... 21 4.3.1Local Migration ................................................................................. 21 4.3.2Remote Migration ............................................................................. 23 4.4 SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP Customer Activity Repository 1.0 ............ 24 4.4.1Remote Migration ............................................................................. 24 4.5 SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA to SAP Customer Activity Repository 1.0 .......................... 25 4.5.1Remote Migration ............................................................................. 25

Executing the POS Transaction Data Migration Report ....... 26 5.1 POS Transaction Data Migration Report........................................ 27 5.1.1Migration Path and Type ................................................................. 27 5.1.2POS Data Selection .......................................................................... 28 5.1.3Processing Control .......................................................................... 28

8 July 2014

5.2 Migration and Task Processing ...................................................... 29 5.3 Migration and Extensions ............................................................... 29 5.4 Choosing Between the Remote and Local Options ...................... 30 5.4.1Remote Migration ............................................................................. 30 5.4.2Local Migration ................................................................................. 31

Testing POS Transaction Data Migration .............................. 33 6.1 Testing Procedure ............................................................................ 33

SAP Notes for the Migration

July 2014 9

Document History

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace http://service.sap.com/instguides.

The following table provides an overview on the most important document changes: Version Date Description 1.03 2014-07-07 Added prerequisite to disable category code determination

until POS transaction data migration is completed. 1.02 2014-04-03 Updates to information about local migration. 1.01 2014-03-26 References to important SAP Notes added. 1.00 2013-07-24 Initial Version

SAP Notes for the Migration

10 July 2014

Why is POS Transaction Data Migration Necessary?

There are three SAP applications that allow you to receive and process POS Transaction data from connected stores:

SAP NetWeaver BI Content (version 7.x6 or earlier) SAP POS Data Management (SAP POS DM) 1.0, installed on either:

o SAP NetWeaver BW on a traditional RDBMS o SAP NetWeaver BW powered by SAP HANA

SAP Customer Activity Repository 1.0 When your project involves transitioning from one of these applications to another using the available migration paths then you need to consider whether you want to move the POS transaction data stored by your existing application to the new application.

Migrate POS Transaction Data: If you want to re-use POS transaction data already accumulated by your existing (source) application in your new (target) application, you must plan and execute a POS transaction data migration as a dedicated project.

We recommend that the migration of POS transaction data is planned as a separate project by your implementation team, with sufficient time and resources allocated to this project. Inadequate setup or execution of the migration process carries the significant risk of data loss and it is essential that all relevant data is backed up prior to executing the migration process. The migration should be carried out by consultants who are experienced with either SAP POS DM 1.0, installed on SAP NetWeaver BW powered by SAP HANA or SAP Customer Activity Repository. The remainder of this guide provides information on migrating your existing POS transaction data to your new application.

Do not Migrate POS Transaction Data: If you do not want to re-use POS transaction data already accumulated by your existing application in your new application, simply store it in your existing application. All the new POS transactions sent by connected stores will be received by your new application. All the existing POS transaction data stored in your existing application will remain in the existing application until you no longer need it, at which point, you simply archive this data. The contents of this guide do not apply to your situation.

SAP Notes for the Migration

July 2014 11

2.1 SAP Notes for the Migration You must read the following SAP Notes before you start the migration. These SAP Notes contain the most recent information on the migration, as well as corrections to the migration documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes. SAP Note Number

Title Description

1905976 Local TLOG data migration

Corrections to the local migration process for POS transaction migration from SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

1918627 Migrate content from TLOGS to TLOGF

Correction to the migration process.

1930573 DATASTATUS wrong in table /posdw/tlogf

Corrections and links to related SAP Notes with regards to maintenance of the data status value during the migration process.

2.2 Standard SAP Data Provisioning/Replication Mechanisms

Data provisioning and data replication are activities frequently performed to move data from one database/system to another database/system. Standard SAP mechanisms exist to perform this data movement. Some of these standard mechanisms include:

Trigger-Based Data Replication Using SAP Landscape Transformation Replication Server The SAP Landscape Transformation (LT) Replication Server is an SAP technology that allows you to load and replicate data in real-time from SAP source systems and non-SAP source systems to an SAP HANA environment. For more information, see:

o SAP HANA Installation Guide – Trigger-Based Replication (SLT), located at http://help.sap.com/hana_platform Installation and Upgrade Information Data Replication Installation Guides o http://help.sap.com/nw_platform Application Help Function-Oriented View Business Warehouse Data Warehousing ModelingData Acquisition Transferring Data Using Staging BAPIs Transferring Data with SAP Landscape Transformation Replication Server

Standard SAP Data Provisioning/Replication Mechanisms

12 July 2014

Data Management with SAP BusinessObjects Data Services SAP BusinessObjects Data Services blends batch extraction, transformation, and loading (ETL) technology with real-time bi-directional data flow across multiple applications for the extended enterprise. For more information, see:

o http://help.sap.com/bods o http://help.sap.com/nw_platform Application Help Function-Oriented View Business Warehouse Data Warehousing ModelingData Acquisition Transferring Data Using Staging BAPIs Transferring Data with SAP Data Services

SAP Sybase Replication Server SAP Sybase Replication Server is database replication software that moves and synchronizes data across the enterprise to meet a host of competing needs, including guaranteed data delivery, real-time business intelligence and zero operational downtime. For more information, see:

o http://www.sybase.com/products/businesscontinuity/replicationserver At the time of the publishing of this guide, this link provided information about the SAP Sybase Replication Server.

SAP HANA Direct Extractor Connection (DXC) The SAP HANA Direct Extractor Connection (DXC) is a means for providing foundation data models that are based on SAP Business Suite entities to SAP HANA. Entities modeled in the SAP Business Suite are, in many cases, very complex. Application logic, in the form of SAP Business Content DataSource Extractors, has been available as the basis for data modeling and data acquisition for SAP NetWeaver Business Warehouse. DXC allows you to leverage existing SAP Business Content DataSource Extractors to deliver data to SAP HANA. For more information, see:

o http://help.sap.com/hana_platform Installation and Upgrade InformationData Replication Installation GuidesSAP HANA Direct Extractor Connection Implementation Guide

Standard SAP Data Provisioning/Replication Mechanisms

July 2014 13

2.2.1 Ineffectiveness of Standard Data Provisioning for POS Transaction Data Migration

There are several reasons why you cannot use the standard SAP data provisioning/replication mechanisms to migrate POS transaction data from POS Data Management in SAP NetWeaver BI Content (version 7.x6 or earlier) or SAP POS DM 1.0 to SAP Customer Activity Repository 1.0. These include:

SAP Customer Activity Repository, a new installation: SAP Customer Activity Repository 1.0 is a new product and you cannot upgrade from SAP NetWeaver BI Content (version 7.x6 or earlier) or SAP POS DM 1.0 to SAP Customer Activity Repository 1.0. As a result, the SAP Customer Activity Repository system does not contain any POS transaction records until you migrate the POS transaction data from the source SAP NetWeaver BI Content (version 7.x6 or earlier) or SAP POS DM 1.0 system. Data storage discrepancies: POS Data Management in SAP NetWeaver BI Content (version 7.x6 or earlier) and SAP POS DM 1.0 installed on SAP NetWeaver BW on a traditional RDBMS compress and store POS transaction data in binary format (binary large object database field or BLOBs) in either the /POSDW/TLOGS or the /POSDW/TLOGL table (depending on the overall transaction size). SAP Customer Activity Repository 1.0 stores transactions in an uncompressed format in the /POSDW/TLOGF table. The /POSDW/TLOGF table flattens out the internal structure of the TLOG (/POSDW TRANSACTION_INT). This table is column-based and does not contain BLOB fields. Field discrepancies: New fields have been added to the internal TLOG structure (/POSDW TRANSACTION_INT) in SAP Customer Activity Repository 1.0. Consequently, matching database fields have been added to the POSDW/TLOGF table. These additional fields are only populated during inbound processing of POS transactions.

Because you cannot use the standard SAP data provisioning/replication mechanisms, the POS Transaction Data Migration Report has been introduced in both SAP POS DM 1.0 SP02 and SAP Customer Activity Repository applications. This report allows you to migrate POS transaction data from a source system to a target system by simulating the POS Data Management inbound processing. For more information on this report, see section Executing the POS Transaction Data Migration Report.

Supported Migration Paths

14 July 2014

2.3 Supported Migration Paths Here, we need to identify which of the following paths are in scope. Migration Path Migration Required

Due To: Source: Target: SAP NetWeaver BI Content (version 7.x6 or earlier)

SAP POS DM 1.0, installed on SAP NetWeaver BW powered by SAP HANA

Major structure differences between the /POSDW/TLOGS or /POSDW/TLOGL table and the /POSDW/TLOGF table.

Unavailability of a number of additional fields in the /POSDW/TLOGS or /POSDW/TLOGL tables that exist in the /POSDW/TLOGF.

SAP NetWeaver BI Content (version 7.x6 or earlier)

SAP Customer Activity Repository 1.0

SAP Customer Activity Repository 1.0 always requires a new system installation. Major structure differences between the /POSDW/TLOGS or /POSDW/TLOGL table and the /POSDW/TLOGF table. Availability of a number of additional fields in the /POSDW/TLOGF table that do not exist in the /POSDW/TLOGS or /POSDW/TLOGL table.

SAP POS DM 1.0, installed on SAP NetWeaver BW on a traditional RDBMS

SAP POS DM1.0, installed on SAP NetWeaver BW powered by SAP HANA

Major structure differences between the /POSDW/TLOGS or /POSDW/TLOGL table and the /POSDW/TLOGF table.

Unavailability of a number of additional fields in the /POSDW/TLOGS or /POSDW/TLOGL tables that exist in the /POSDW/TLOGF.

Out of Scope

July 2014 15

SAP POS DM 1.0, installed on SAP NetWeaver BW on a traditional RDBMS

SAP Customer Activity Repository 1.0

SAP Customer Activity Repository 1.0 always requires a new system installation. Major structure differences between the /POSDW/TLOGS or /POSDW/TLOGL table and the /POSDW/TLOGF table. Availability of a number of additional fields in the /POSDW/TLOGF table that do not exist in the /POSDW/TLOGS or /POSDW/TLOGL table.

SAP POS DM 1.0, installed on SAP NetWeaver BW powered by SAP HANA

SAP Customer Activity Repository 1.0

SAP Customer Activity Repository 1.0 always requires a new system installation. Availability of a number of additional fields in the /POSDW/TLOGF table in SAP Customer Activity Repository that do not exist in the /POSDW/TLOGF table in SAP POD DM 1.0.

2.4 Out of Scope This guide does not include instructions for migrating POS transaction data that has been archived. You can reload archived POS transaction data into the source system and follow the instructions provided in this guide to migrate this data to your target system.

Prerequisites

16 July 2014

Planning Your Migration Project 3.1 Prerequisites Prior to migrating POS transaction data, do the following:

Read this guide in its entirety. Identify the migration path that is applicable to your project.

The possible POS transaction data migration paths are outlined in the Supported Migration Paths section.

Choose between the remote and local migration options as described in the Choosing Between the Remote and Local Options section. Pay particular attention to the prerequisites of the selected option.

Purchase and install the required systems/products. Plan time and resources for the execution of the migration project. Examine your Customizing settings on the target system, and disable any tasks set to Immediate Processing. For more information, see the Migration and Task Processing section. Examine your Customizing settings on the target system, and temporarily disable the Category Code Determination feature until the migration has been completed. In Customizing for SAP Customer Activity Repository, choose POS Data Management -> POS Inbound Processing -> General Settings -> Define General Settings and ensure the Filter Value for Cat. Code Determin. field is left blank.

3.2 Assumptions The instructions for migrating POS transaction data included in this guide are provided given the following assumptions:

You want to use the POS transactional data that you have accumulated on your source system (that is, the system you are migrating from) on your new target system (that is, the system you are migrating to).

The migration is performed by a team of technical consultants with expertise in SAP NetWeaver and SAP POS DM.

SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

July 2014 17

Migration Paths and Options This section provides details on executing the POS Transaction Data Migration Report based on the chosen migration path and option. The POS Transaction Data Migration Report has two options for performing the migration of POS transaction data: local migration or remote migration. For more information on each of these options, see section Choosing Between the Remote and Local Options.

4.1 SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

Previously, POS Data Management functionality was integrated directly in the SAP NetWeaver BI Content (version 7.x6 or earlier). As of SAP NetWeaver BI Content (version 7.x7), SAP POS DM 1.0 is shipped separately from SAP NetWeaver BI Content, as a distinct product. This subsection describes how to migrate POS transaction data from SAP NetWeaver BI Content 7.x6 (version 7.x6 or earlier) to SAP POS DM 1.0 installed on SAP NetWeaver BW powered by SAP HANA.

4.1.1 Local Migration Use this option if you have performed or are planning to perform a migration of an existing SAP NetWeaver BW installation running on a traditional RDBMS database to SAP NetWeaver BW powered by SAP HANA.

If you are planning an initial installation of SAP NetWeaver BW powered by SAP HANA, read the Remote Migration section.

During the SAP NetWeaver BW migration, a heterogeneous system copy from the existing source system to the target system must be performed. The heterogeneous system copy includes the copying of tables /POSDW/TLOGS and /POSDW/TLOGL, as well as their content, to the target system. For more information on the heterogeneous system copy and the initial installation of SAP NetWeaver Business Warehouse on the SAP HANA database, refer to the Planning section of the System Copy Guide for SAP Systems Based on SAP NetWeaver Application Server ABAP on <Your Database> found on the SAP Service Marketplace under https://service.sap.com/instguidesSAP NetWeaver 7.3 Installation System Copy Software provisioning manager 1.0 system copy guide. Once you have migrated your existing SAP NetWeaver BW installation to SAP NetWeaver BW powered by SAP HANA, you must also install or upgrade to SAP POS DM 1.0 SP02, or higher, on the target system as described in SAP Notes 1683825 and 1683826.

SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

18 July 2014

As of SAP POS DM 1.0 SP02, the POS Transaction Data Migration Report is available directly in the application (launched using transaction /N/POSDW/MIGR). When you execute the POS Transaction Data Migration Report on the target system, the migration of the POS transaction data is executed according to the displayed path:

During local migration, the POS Transaction Data Migration Report will not create new transaction indices for the migrated transactions. Instead, it will re-use existing transaction indices (table /POSDW/NAVIX), which were copied to the target system during the heterogeneous system copy. This ensures that all existing transaction relevant information, such as transaction indices, processing logs and transaction task statuses, is preserved as it was in the source system. For information on archiving POS transaction data following a local migration, see 5.4.2.1 Archiving Migrated Data Following Local Migration.

SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

July 2014 19

4.1.2 Remote Migration Use this option if you have performed or are planning to perform an initial installation of SAP NetWeaver BW powered by SAP HANA. That is, you are not planning to perform a system copy from an existing SAP NetWeaver BW installation running on a traditional RDBMS database to an SAP NetWeaver BW powered by SAP HANA. In SAP NetWeaver BI Content (version 7.x6 or earlier), the POS Transaction Data Migration Report does not exist. Therefore, before performing the migration using the remote option, you must create the POS Transaction Data Migration Report in your namespace, as described in SAP Note 1766578. When you execute the POS Transaction Data Migration Report on the source system, the migration of the POS transaction data to the target system is executed according to the displayed path:

SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP Customer Activity Repository 1.0

20 July 2014

4.2 SAP NetWeaver BI Content (Version 7.x6 or Earlier) to SAP Customer Activity Repository 1.0

SAP Customer Activity Repository 1.0 always requires a new system installation and there is no supported upgrade path from SAP NetWeaver BI Content (version 7.x6 or earlier) to SAP Customer Activity Repository 1.0. Therefore, it is impossible to perform a heterogeneous system copy from the existing system to the target system. As a result, local migration is not supported to migrate POS transaction data from SAP NetWeaver BI Content (version 7.x6 or earlier) to SAP Customer Activity Repository 1.0. Only the remote migration option is supported.

4.2.1 Remote Migration In SAP NetWeaver BI Content (version 7.x6 or earlier), the POS Transaction Data Migration Report does not exist. Therefore, before performing the migration using the remote option, you must create the POS Transaction Data Migration Report in your namespace, as described in SAP Note 1766578. When you execute the POS Transaction Data Migration Report on the source system, the migration of the POS transaction data to the target system is executed according to the displayed path:

SAP HANA

SAP NetWeaver BW SAP NetWeaverSAP Customer Activity Repository

ABAPABAP

RDBMS

POS Transactions/POSDW/TLOGS /POSDW/TLOGL

RFC

POS Transactions/POSDW/TLOGF

POS Inbound Processing Engine

SAP NetWeaverBI Content

TLOG Migration Report(Customer namespace)

SAP POS DM

SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

July 2014 21

4.3 SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

4.3.1 Local Migration Use this option if you have performed or are planning to perform a migration of an existing SAP NetWeaver BW installation running on a traditional RDBMS database to SAP NetWeaver BW powered by SAP HANA.

If you are planning an initial installation of SAP NetWeaver BW powered by SAP HANA, read the Remote Migration section.

During the SAP NetWeaver BW migration, a heterogeneous system copy from the existing source system to the target system must be performed. The heterogeneous system copy includes the copying of tables /POSDW/TLOGS and /POSDW/TLOGL, as well as their content, to the target system. For more information on the heterogeneous system copy and the initial installation of SAP NetWeaver Business Warehouse on the SAP HANA database, refer to the Planning section of the System Copy Guide for SAP Systems Based on SAP NetWeaver Application Server ABAP on <Your Database> found on the SAP Service Marketplace under https://service.sap.com/instguidesSAP NetWeaver 7.3 Installation System Copy Software provisioning manager 1.0 system copy guide. Once you have migrated your existing SAP NetWeaver BW installation to SAP NetWeaver BW powered by SAP HANA, you must also install or upgrade to SAP POS DM 1.0 SP02, or higher, on the target system as described in SAP Notes 1683825 and 1683826.

SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

22 July 2014

As of SAP POS DM 1.0 SP02, the POS Transaction Data Migration Report is available in the application (launched using transaction /N/POSDW/MIGR). When you execute the POS Transaction Data Migration Report on the target system, the migration of the POS transaction data is executed according to the displayed path:

During local migration, the POS Transaction Data Migration Report will not create new transaction indices for the migrated transactions. Instead, it will re-use existing transaction indices (table /POSDW/NAVIX), which were copied to the target system during the heterogeneous system copy. This ensures that all existing transaction relevant information, such as transaction indices, processing logs and transaction task statuses, is preserved as it was in the source system. For information on archiving POS transaction data following a local migration, see 5.4.2.1 Archiving Migrated Data Following Local Migration.

SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA

July 2014 23

4.3.2 Remote Migration Use this option if you have performed or are planning to perform an initial installation of SAP NetWeaver BW powered by SAP HANA. That is, you are not planning to perform a system copy from an existing SAP NetWeaver BW installation running on a traditional RDBMS database to an SAP NetWeaver BW powered by SAP HANA. If your source system contains SAP POS DM 1.0 SP01, you must apply SAP Note 1854668 to create the POS Transaction Data Migration Report on your source system. When you execute the POS Transaction Data Migration Report on the source system, the migration of the POS transaction data to the target system is executed according to the displayed path:

SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP Customer Activity Repository 1.0

24 July 2014

4.4 SAP POS DM 1.0, Installed on SAP NetWeaver BW on a Traditional RDBMS to SAP Customer Activity Repository 1.0

SAP Customer Activity Repository 1.0 always requires a new system installation and there is no supported upgrade path from SAP POS DM 1.0 installed on SAP NetWeaver BW on a traditional RDBMS to SAP Customer Activity Repository 1.0. Therefore, it is impossible to perform a heterogeneous system copy from the existing system to the target system. As a result, local migration is not supported to migrate POS transaction data from SAP POS DM 1.0 installed on SAP NetWeaver BW on a traditional RDBMS to SAP Customer Activity Repository 1.0. Only the remote migration option is supported.

4.4.1 Remote Migration If your source system contains SAP POS DM 1.0 SP01, you must apply SAP Note 1854668 to create the POS Transaction Data Migration Report on your source system. When you execute the POS Transaction Data Migration Report on the source system, the migration of the POS transaction data to the target system is executed according to the displayed path:

SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA to SAP Customer Activity Repository 1.0

July 2014 25

4.5 SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA to SAP Customer Activity Repository 1.0

SAP Customer Activity Repository 1.0 always requires a new system installation and there is no supported upgrade path from SAP POS DM 1.0 installed on SAP NetWeaver BW powered by SAP HANA to SAP Customer Activity Repository 1.0. Therefore, it is impossible to perform a heterogeneous system copy from the existing system to the target system. As a result, local migration is not supported to migrate POS transaction data from SAP POS DM 1.0 installed on SAP NetWeaver BW powered by SAP HANA to SAP Customer Activity Repository 1.0. Only the remote migration option is supported.

4.5.1 Remote Migration If your source system contains SAP POS DM 1.0 SP01, you must apply SAP Note 1854668 to create the POS Transaction Data Migration Report on your source system. When you execute the POS Transaction Data Migration Report on the source system, the migration of the POS transaction data to the target system is executed according to the displayed path:

SAP HANA

DB SchemaSAP_CAR

SAP NetWeaver BW SAP NetWeaverSAP Customer Activity Repository

ABAPABAP

SAP POS DMTLOG Migration

ReportRFC

POS Transactions/POSDW/TLOGF

POS Inbound Processing Engine

DB SchemaSAP_CAR

POS Transactions/POSDW/TLOGF

SAP NetWeaverBI Content

SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA to SAP Customer Activity Repository 1.0

26 July 2014

Executing the POS Transaction Data Migration Report

The POS Transaction Data Migration Report allows you to migrate POS transaction data from a source system to a target system according to the migration paths and options described in the sections above.

The POS Transaction Data Migration Report simulates the POS Data Management inbound processing to migrate the POS transaction data. The standard inbound interface is triggered in the target system through the call of the standard RFC interface (/POSDW/CREATE_TRANSACTIONS_EXT) and the inbound processing is carried out according to the Customizing in the target system. The POS transaction data in the source system might reside in:

1. /POSDW/TLOGS and /POSDW/TLOGL tables in a compressed format; 2. /POSDW/TLOGF table in an uncompressed, flat format. The POS transaction data in the target system will reside in:

1. /POSDW/TLOGF table in an uncompressed, flat format. You launch the POS Transaction Data Migration Report using transaction /N/POSDW/MIGR. You can run the report on the source system and perform a remote

POS Transaction Data Migration Report

July 2014 27

migration to the target system, or you can run the report on the target system and perform a local migration. The POS Transaction Data Migration Report supports parallel processing and you can restrict the migration process to selected stores, days and transaction indices.

5.1 POS Transaction Data Migration Report This section explains the various options of the POS Transaction Data Migration Report.

5.1.1 Migration Path and Type

You must specify the Source POS Transaction Data Table:

1. /POSDW/TLOGS: Use this option if your POS transaction data resides in /POSDW/TLOGS and /POSDW/TLOGL tables. For example, use this setting when migrating POS transaction data from SAP NetWeaver BI Content (version 7.x6 or earlier) to SAP Customer Activity Repository. 2. /POSDW/TLOGF: Use this option if your POS transaction data reside in the new /POSDW/TLOGF table. For example, use this setting when migrating POS transaction data from SAP POS DM 1.0, installed on SAP NetWeaver BW powered by SAP HANA to SAP Customer Activity Repository.

You must specify the Migration Type:

1. Local: Use this option to run the POS Transaction Data Migration Report in the target system and do a local migration to the /POSDW/TLOGF table. Local migration can only be performed if a heterogeneous system copy has been performed beforehand. The heterogeneous system copy moves all the required POS transaction data in the /POSDW/TLOGS and /POSDW/TLOGL tables from the source system to the target system.

You cannot use this option to migrate POS transaction data to SAP Customer Activity Repository 1.0. 2. Remote: Use this option to run the POS Transaction Data Migration Report in the source system and perform a remote migration to the target system. This option requires that you enter a trusted RFC destination representing the connection to the target system.

POS Transaction Data Migration Report

28 July 2014

5.1.2 POS Data Selection

Under POS Data Selection, you select a range of stores, business days and/or transaction indices that will determine which POS transaction records to migrate from the source to the target system.

5.1.3 Processing Control

Under Processing Control, you have options to control the runtime behavior of the POS Transaction Data Migration Report and the resulting log information. The Package Size setting controls the number of POS transactions sent in a single call to the standard RFC interface (/POSDW/CREATE_TRANSACTIONS_EXT). This setting is considered regardless of whether the /POSDW/CREATE_TRANSACTIONS_EXT interface is called locally or remotely (using a trusted RFC destination). The Package Size setting indirectly controls the frequency of database commits in the target system, since a commit is performed after each call to the /POSDW/CREATE_TRANSACTIONS_EXT interface. By setting the Parallel Processing indicator, you can choose to use parallel task processing to run the report, similar to other standard POS Data Management reports (for example, the PIPE Processing of Inbound Queue for POS Transactions (/N/POSDW/QDIS) or the PIPE Outbound Processing (/N/POSDW/ODIS) reports). Furthermore, you can set the maximum number of parallel processes to a value that you judge to be optimal and that can be handled by your system. The system will perform the parallel task processing by business day, that is, for each business day in the selection range, a separate parallel task is executed. You can also choose whether or not to issue a processing log when the POS Transaction Data Migration Report is executed. The Business Application Log (BAL) framework is used to create the processing log. If you choose to issue a log, the results of the migration are displayed in a separate window, which opens when the migration processing is complete. You can also access the processing log at a later time using transaction SLG1. You can choose to permanently save the processing log by setting the Save Log indicator.

Migration and Task Processing

July 2014 29

5.2 Migration and Task Processing Typically, during productive use of SAP POS DM or SAP Customer Activity Repository, there are tasks that are set to Immediate Processing in the Define Tasks, Define Aggregation Tasks and Define Outbound Tasks Customizing activities.

The Immediate Processing setting indicates that a task will be automatically performed on a POS transaction during inbound processing. The POS Transaction Data Migration Report simulates the POS Data Management inbound processing to migrate POS transaction data, taking into account the current Customizing settings on the target system. This means, that if you have some tasks set to Immediate Processing, these will be executed on the POS transactions when these are moved from the source system to the target system by the POS Transaction Data Migration Report. Task processing should not be performed during the migration process. Not only is it unnecessary (presumably, all tasks have been executed on the transactions in the source system), but it can also significantly and needlessly slow down the migration process. Prior to using the POS Transaction Data Migration Report, examine the Customizing settings on the target system, and disable any tasks set to Immediate Processing.

5.3 Migration and Extensions If you have extended the POS Data Management transaction log (TLOG) data model using the extension segments provided for this purpose in the /POSDW/TRANSACTION_INT structure, the data stored in these extension segments will be migrated using the POS Transaction Data Migration Report.

WARNING: If you have extended your TLOG data model in any other way than using the provided extension segment concept, the POS Transaction Data Migration Report will not migrate the data contained within your custom extensions.

Furthermore, the data stored in the extension segments will be migrated taking in account the setting of the Store Extensions in Separate Table option in the Define General Settings Customizing activity. Based on this Customizing setting, the extensions are stored either directly in the /POSDW/TLOGF table, or in a dedicated /POSDW/TLOGF_EXT table.

Choosing Between the Remote and Local Options

30 July 2014

5.4 Choosing Between the Remote and Local Options

The POS Transaction Data Migration Report has two options for performing the migration of POS transaction data: remote migration or local migration.

5.4.1 Remote Migration In this approach, the POS Transaction Data Migration Report is executed on the source system (that is, the system you are migrating from). The report reads POS transaction data from the local /POSDW/TLOGS,/POSDW/TLOGL or /POSDW/TLOGF tables and writes the transaction data in the remote /POSDW/TLOGF table on the target system (that is, the system you are migrating to) by calling the standard RFC interface (/POSDW/CREATE_TRANSACTIONS_EXT) to create transactions. A trusted RFC connection must exist between the source and the target systems.

Choosing Between the Remote and Local Options

July 2014 31

5.4.2 Local Migration In this approach, the POS Transaction Data Migration Report is executed on the target system (that is, the system you are migrating to). It reads transaction data from the local /POSDW/TLOGS and /POSDW/TLOGL tables and writes the transaction data in the local /POSDW/TLOGF table in the target system (again, the system you are migrating to) by calling the standard local interface to create transactions (/POSDW/CREATE_TRANSACTIONS_EXT). Prior to executing a local migration, you must perform a heterogeneous system copy from the source system (that is, the system you are migrating from) to the target system to make the contents of the /POSDW/TLOGS and /POSDW/TLOGL tables available in the target system. For more information on performing the heterogeneous system copy and the initial installation of SAP NetWeaver Business Warehouse on the SAP HANA database, refer to the Planning section of the System Copy Guide for SAP Systems Based on SAP NetWeaver Application Server ABAP on <Your Database> found on the SAP Service Marketplace under https://service.sap.com/instguidesSAP NetWeaver 7.3 Installation System Copy Software provisioning manager 1.0 system copy guide. In the local migration approach, all processing is done locally in the target system; therefore, better migration performance is expected. However, you must factor in the potential increase in system RAM requirements caused by the temporary duplication of transactional data during the heterogeneous system copy. During local migration, the POS Transaction Data Migration Report will not create new transaction indices for the migrated transactions. Instead, it will re-use existing transaction indices (table /POSDW/NAVIX), which were copied to the target system during the heterogeneous system copy. This ensures that all existing transaction relevant information, such as transaction indices, processing logs and transaction task statuses, is preserved as it was in the source system.

Choosing Between the Remote and Local Options

32 July 2014

5.4.2.1 Archiving Migrated Data Following Local Migration

After a successful local migration, we recommend the following strategy for archiving POS transaction data stored in /POSDW/TLOGS and /POSDW/TLOGL tables: 1. On the source system, archive the POS transactions stored in tables /POSDW/TLOGS/L using the dedicated archiving object /POSDW/TL.

Do not archive POS transactions stored in tables /POSDW/TLOGS/L on the target (SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA) system. Archiving contents of tables /POSDW/TLOGS/L on the target system would also archive the contents of complementary tables, such as /POSDW/NAVIX or /POSDW/TSTAT, which are referenced from the /POSDW/TLOGF table. 2. On the target (SAP POS DM 1.0, Installed on SAP NetWeaver BW Powered by SAP HANA) system, delete the data from both the /POSDW/TLOGS and /POSDW/TLOGL tables. This data has been archived in the previous step, and is no longer needed.

Testing Procedure

July 2014 33

Testing POS Transaction Data Migration

This section contains a testing procedure that you can use to test the migration of POS transaction data from SAP POS DM 1.0, installed on SAP NetWeaver BW on a traditional RDBMS to SAP Customer Activity Repository 1.0.

6.1 Testing Procedure Verify that you have access to two systems: Source system: SAP POS DM 1.0, installed on SAP NetWeaver BW on a traditional

RDBMS Target system: SAP Customer Activity Repository 1.0

The following prerequisites must be met: You should have at least one valid store (for example Store 1). You must have POS transactional data that exists for Store 1 for a particular business

date (for example, 01.01.2013). A trusted RFC connection is established between the source and the target systems.

On the target system (SAP Customer Activity Repository 1.0), clear the /POSDW/TLOGF table for the chosen business date.

The assumption is that you are not yet using the target system productively, and therefore, all the transactions that you might have stored in the /POSDW/TLOGF table are test transactions that can be deleted.

i. On the target system (SAP Customer Activity Repository 1.0), use transaction /N/POSDW/DELE.

ii. Enter Store 1 in the Store field iii. Enter 01.01.2013 in the Posting Date field and click Execute.

On the source system (SAP POS DM 1.0, installed on SAP NetWeaver BW on a traditional RDBMS), execute the POS Transaction Data Migration Report to perform a remote migration of POS transaction data. i. On the source system (SAP POS DM 1.0, installed on SAP NetWeaver BW on a

traditional RDBMS), use transaction /N/POSDW/MIGR. ii. Select /POSDW/TLOGS as the Source POS Transaction Data Table. iii. Select Remote as the Migration Type. iv. Enter the name of the target system (SAP Customer Activity Repository 1.0) in the

RFC Destination field. v. Enter Store 1 in the Store field. vi. Enter 01.01.2013 in the Business Day field and click Execute.

Testing Procedure

34 July 2014

On the target system (SAP Customer Activity Repository 1.0), verify that the POS transactions have been migrated to the /POSDW/TLOGF table for the chosen business date i. On the target system (SAP Customer Activity Repository 1.0), use transaction

SE16. ii. Enter /POSDW/TLOGF in the Table Name field. iii. Click the Table Contents icon. iv. Enter Store 1 in the RETAILSTOREID field and click Execute. v. Verify that all the transaction indices for BUSINESSDAYDATE 01.01.2013 have

been migrated. Verify that the number of the transactions and their content is identical.