SAP FAQ

Applicable Releases:

All releases mentioned in the prerequisites of the configuration guide.

This FAQ Document is intended to give the readers an answer to frequently asked questions related to the BW PCA functionality. The document is still “work in progress”, so this guide is not intended to be exhaustive so far, and might never be. The purpose of this document is to deliver additional information besides SAP Help and Blogs to get a better understanding of the concepts of BW PCA.

Please note that this document will no more be updated. The latest Version of the FAQs can be

found on SCN page: http://scn.sap.com/docs/DOC-39505

Version 1.5

May 2014

BW PCA FAQ – Frequently Asked Questions related to BW Post Copy Automation

© Copyright 2015 SAP AG. All rights reserved. No part of this publication may be reproduced or tran smitt ed in any form or for any purpose wi thout the express p ermission of SAP AG. Th e information cont ained herein may b e changed without prior notice.

Some softw are products market ed by SAP AG and its dist ributors contain propri et ary softw are component s of other software vendors. Microsoft, Windows , Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM , DB2, D B2 Universal Datab ase, Syst em i, System i5, System p, Syst em p5, Syst em x, Syst em z, System z 10, Syst em z9, z 10, z 9, iSeries, pSeries, xSeri es, z Series , eServer, z/VM, z /O S, i5/O S, S/390 , OS/390, O S/4 00, AS/400, S/390 Parall el Enterp rise Server, Po werVM, Pow er Archit ecture, POWE R6+, PO WER6 , PO WER5 +, PO WE R5, PO WER, OpenPow er, PowerPC, Bat chPipes, Bl ad eCenter, System Storage, G PFS, H ACMP, RET AIN, D B2 Connect, RACF, Redbooks, OS/2, Parall el Sysplex, MVS/E SA, AIX,

Intelligent Miner, WebSph ere, N etfinity, Tivoli and Informix are trademarks or regist ered trad emarks 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 eith er trademarks or regist ered t rad emarks of Adobe Systems In corporated in the United Stat es and /or other countries. Oracl e is a regist ered trad emark of Oracle Corporation.

UNIX, X/Op en, OSF /1, and Motif are regist ered trademarks of the Open G roup.

Citrix, ICA, Program N eighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trad emarks or regist ered trad emarks of Citrix Systems, Inc.

HTML, XML, XH TML and W3C are t rad emarks or registered trademarks of W3C®, World Wid e Web Consortium, M ass achus etts Institut e of Technology.

Jav a is a registered trademark of Sun Micro syst ems, Inc. Jav aScript is a registered trademark of Sun Microsyst ems, Inc., used under licen se for technology invented and i mplement ed by N etscape.

SAP, R/3, SAP N etWeaver, Duet, Partn erEdge, ByDesign, SAP BusinessObjects Explorer, StreamWo rk, and other SAP product s and se rvices mentioned herein as well as thei r respective logos are trademarks or regist ered trad emarks of SAP AG in Germany and other co untries.

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. Sybase and Adapti ve Serv er, iAnywh ere, Sybas e 365, SQL Anywhere, and other Sybas e products and services mentioned herein as well as thei r respective logos are trademarks or regist ered t rad emarks of Sybase, Inc. Sybase is an SAP comp any.

All other product and service names mentioned are the trademarks of their resp ectiv e co mpani es. Dat a cont ained in this document serves information al purposes only. N ational product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may b e rep roduced, cop ied, or trans mitted in an y form or for any purpos e without the express prior writ ten permis sion of SAP AG. This document is a preli minary v ersion and not subject to your licens e agreement or any other agreement with SAP. This document contains only int ended strat egies, d evelop ments , and functionalities of the SAP® product and is not intended to be binding upon SAP to an y parti cular course of business , product strategy, and /or dev elopment. Pl eas e note that this docu ment is subject to ch ange and may be ch anged by SAP at any ti me without notice.

SAP assu mes no responsibility for errors or omissions in this document. SAP does not w arrant the accuracy or compl et eness of the information, text, graphics, links , or other items contained within this mat erial . This document is provided without a warrant y of any kind, either express or i mplied, including but not limited to the i mplied w arr anties of merchant ability, fitness for a particular purpose, or non-infringement.

SAP sh all hav e no liability for damages of any kind including without limit ation direct , special, indirect , or consequ ential d amages that may result from the us e of these materi als. Thi s limit ation shall not apply in cases of intent or gross negligence.

The statutory liability for p ersonal injury and defectiv e products is not affected. SAP has no control over the information that you may access th rough the use of hot links contained in thes e materials and does not endors e your use of third-party Web pag es nor provide an y warranty whatso ever rel ating to third-part y Web pages .

SAP “How-to” Guides are intended to simplify the product implement-

tation. While specific product 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

productive 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 product 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 product is only to be used by

SAP’s Support Services and may not be modified or altered in any way.

Document History

Document Version Description

1.00 First draft of this document

1.10 Added Question 1.19

1.20 Added report

1.30 Updated report

1.40 Added SAP note 1932459

1.50 Added SAP note 2014906

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 File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

<Example

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 Description

Caution

Note or Important

Example

Recommendation or Tip

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 1

Table of Contents

1. BW PCA Initial Copy .............................................................................................................. 2

1.1 LVM license ....................................................................................................................... 2

1.2 Where can I download the software, I can’t find the software in service market

place................................................................................................................................... 2

1.3 Where within SAP do I find more information about BW PCA Initial Copy? .............. 2

1.4 Are there any recorded sessions available? .................................................................. 2

1.5 What are the required SAP notes I have to implement? .............................................. 2

1.6 What are the task lists I have to execute and in which system do I have to do

that? ................................................................................................................................... 2

1.7 Should the customer continue the execution of the task list

SAP_BW_COPY_INITIAL_PREPARE (i.e. after the step Confirm export) in the

copied system?................................................................................................................. 3

1.8 Should I update the configuration of the original delivered task lists? ....................... 3

1.9 What happens to my ECC environment? Do I have to lock ECC against changes? .. 3

1.10 What happens during the cloning process and what are things I should consider: .. 3

1.11 Which delta queues get cloned? ..................................................................................... 3

1.12 What should I consider once the delta queues get very large in between the single

phases I am able to extract towards the connected BW? ............................................ 4

1.13 Is there an RDS solution available? ................................................................................ 4

1.14 What is the install footprint for BW PCA? ...................................................................... 4

1.14.1 What is the impact on the ECC system? .......................................................... 4

1.14.2 What is the impact on the BW system? ............................................................ 5

1.15 How long will the execution of the task list take in the cloned system ....................... 5

1.16 Are there further task list which are interesting for me? ............................................. 5

1.17 When the original BW is decommissioned, the original delta queues should not be

filled anymore. What is the advised method of deleting these delta queues? ........... 5

1.18 Which applications do not support BW PCA? ............................................................... 5

1.19 Customer wants to decommission a BW source system or reset the cloned delta

queues created by BW PCA and restart the configuration. What are the required

steps? ................................................................................................................................ 5

1.19.1 Not even in source system A, an entry in table RSBASIDOC exists for BW

system B .............................................................................................................. 5

1.19.2 Within the BW system B, the source system A is visible in the

Administrator Workbench. ................................................................................. 6

1.19.3 Within the BW system B the source System A is not visible in the

Administrator Workbench or does not exist in the metadata tables of BW

system B. But in source system A, in table RSBASIDOC, the entry for

connection towards BW system B is still present. .......................................... 6

2. Appendix .................................................................................. Error! Bookmark not defined.

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 2

1. BW PCA Initial Copy What should you consider when using BW PCA in a BW on HANA migration context?

1.1 LVM license Typically the process starts with getting the license for LVM 1.0 in place. As BW PCA is embedded

into the LVM framework it requires a valid LVM license. The rules are quite clear and follow normal

SAP policy. Customer wanting to use BW PCA Initial Copy, need to contact their Account Executive

/ Global Account Director to get the according license. For questions on licensing please contact

your AE or Solution Management (jeff.anders@sap.com).

Due to involvement of different parties to get the license in place you should start getting the

license early in your project phase.

1.2 Where can I download the software, I can’t find the software in service market place.

Before being able to see the software you have to be registered as a LVM customer. This requires

the license for LVM (see point 1). In case this is in place you find the software under following the

path http://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog

SAP NetWeaver and Complementary Products SAP NW LANDSC VIRT MGT ENT SAP NW

LANDSC VIRT MGT ENT 1.0 Installation.

1.3 Where within SAP do I find more information about BW PCA Initial Copy?

We have created an official SDN page regarding the BW PCA Initial Copy functionality with

presentation material and details which licenses are required, etc.

Please visit http://scn.sap.com/docs/DOC-32414

1.4 Are there any recorded sessions available? We have 2 recorded sessions that should provide an overview of the BW PCA Initial Copy procedure.

a) German session: https://sap.emea.pgiconnect.com/p81522211/

b) English session: http://scn.sap.com/docs/DOC-34256

1.5 What are the required SAP notes I have to implement? To get a list of the notes required in ECC and BW, please execute the report attached to note

http://service.sap.com/sap/support/notes/1707321 in all systems affected by BW PCA. Lessons

learned from customer that used BW PCA is, that you should execute this report with the latest

CSV file in ECC and BW immediately before starting the task list in BW. That ensures that you have

the latest developments / corrections in your systems.

1.6 What are the task lists I have to execute and in which system do I have to do that?

In the original BW you have to execute the task list SAP_BW_COPY_INITIAL_PREPARE. After you

copied the system you execute in the copied system task list

SAP_BW_BASIS_COPY_INITIAL_CONFIG. For details on the procedure please check the

configuration guide.

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 3

1.7 Should the customer continue the execution of the task list SAP_BW_COPY_INITIAL_PREPARE (i.e. after the step Confirm export) in the copied system?

No, the task list SAP_BW_COPY_INITIAL_PREPARE should only be executed in the original BW

system. Please continue the task list after the step Confirm export in the original system BW

system using transaction STC02.

Don’t create a new execution of a task list (e.g. SAP_BW_COPY_INITIAL_PREPARE) via transaction

STC01 while there is already an execution in process. Use transaction STC02 in order to resume

the execution instead.

1.8 Should I update the configuration of the original delivered task lists?

For the SAP_BW_BASIS_COPY_INITIAL_CONFIG task list please do set the missing checkboxes in

the task list SAP_BW_BASIS_COPY_INITIAL_CONFIG, in particular “Configuration of Secure Store

(SECSTORE)”, “Configuration of Transport Management System (STMS)”.

1.9 What happens to my ECC environment? Do I have to lock ECC against changes?

The cloning of the queues can happen without any implication to the operational processes in ECC.

Queues get clones and populated as soon as they are available. Existing queues are not influenced.

1.10 What happens during the cloning process and what are things I should consider:

The cloning of the queues can be divided into 2 phases.

a) The whole procedure starts by executing the step Clone delta queues in BW source system

with the task list SAP_BW_COPY_INITIAL_PREPARE in the original BW system. This step

processes the queues of each configured source system that is connected to BW. The

process clones the relevant queues in the underlying source system by creating the

relevant entries in the metadata tables.

b) In the step Synchronize delta queues in BW source system the task list has to synchronize

the cloned queues with the original queues in the underlying source systems by processing

the single queues sequentially. If you have created a large amount of LUWs in ECC between

the clone step and the synchronization step, the runtime of this step can be significant long.

We have seen in Pilot projects runtimes of up to 5 hours. As a recommendation here you

should empty the queues before cloning by getting deltas into BW. Furthermore you should

keep the time between the clone step and the synchronization step as short as possible.

1.11 Which delta queues get cloned? All deltaqueues which are visible in transaction RSA7 get cloned. Cloning means, we double the

pointers for delta queues, not the data behind. The data is kept in ECC as long as the cloned BW

system hasn’t picked up the deltas. So please consider that in your overall planning as this phase of

growing delta queues should be as short as possible. A good procedure in case you don’t use the

one step migration wizard is the following:

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 4

i) Extract all deltas in the original BW system using standard procedure. Some of our

customer created an own Process Chain that includes all Delta InfoPackages an

executed this Process Chain.

ii) Clone delta queues by executing BW PCA task list SAP_BW_COPY_INITIAL_PREPARE

in original BW system.

iii) Extract all deltas in the original BW system once more (is checked in the BW PCA

procedure).

iv) Synchronize delta queues by continuing BW PCA task list

SAP_BW_COPY_INITIAL_PREPARE in original BW system.

v) Export BW database and start up original BW followed by executing regularly tasks as

you do it usual

vi) Import BW database to build cloned BW system and execute tasklist

SAP_BW_COPY_INITIAL_PREPARE in transaction STC02.

vii) Extract deltas in cloned BW system twice (by using Process Chain from Step i))

viii) Optional upgrade cloned BW system to your target release.

ix) Extract deltas in your upgraded BW system twice (by using Process Chain from Step i))

x) Migrate your database to SAP HANA

xi) Run post migration activities

xii) Extract and execute deltas in BW on HANA on a regularly basis

1.12 What should I consider once the delta queues get very large in between the single phases I am able to extract towards the connected BW?

If the delta queue got very large (e.g. during system copy and HANA Migration) you can use the

parameter MAXPAK in the InfoPackage of a delta upload (->Scheduler –> Data Source Default Data

Transfer) and configure the relevant parameter. See notes

http://service.sap.com/sap/support/notes/1160555 and

http://service.sap.com/sap/support/notes/1231922 for details.

1.13 Is there an RDS solution available? Yes. There is an RDS solution available. In case you want to make yourself familiar with it have a

look at https://service.sap.com/rds-hana-bwmig.

1.14 What is the install footprint for BW PCA? The functionality of BW PCA is delivered via notes and support packages. However in order to use

the tool, you need a license key for LVM. This key is an add-on, so SAP is able to restrict access to

the functionality.

1.14.1 What is the impact on the ECC system? Cloning Queue doesn’t require downtime. There are currently maximum four notes that need to

be applied to your ECC systems: 1570955, 1665834, 1673513, 1736675. Which of those apply to

your system, you can check out using the note analyzer report attached in note 1707321.

The changes applied in the notes rely on existing packages, however mostly new functions, few

changes in existing functions. During execution of the procedure, all delta queues of BW visible

in transaction RSA7 in ECC are doubled, so delta is recorded for a longer time (until both BW

systems got the delta). This must be considered if large delta queues exist in the ECC, as delta

records can only be deleted once both systems extracted the information from ECC already

(growth of ARFCSDATA table).

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 5

1.14.2 What is the impact on the BW system? During the cloning phase (can take a few hours in case of large deltaqueues) delta loads or

initializations of deltas cannot be executed until the cloning process is over and the BW

database is exported. Reporting on existing data is however still possible during that phase until

the BW is shut down for database export.

1.15 How long will the execution of the task list take in the cloned system

We have seen that the runtime is sometimes determined by the runtime of BDLS. In case you

used the BW InfoObject 0LOGSYS in DSOs, InfoCubes or Masterdata objects, the runtime of

BDLS can be significant. Please check in that case whether it would be possible to exclude

tables in the BDLS phase.

1.16 Are there further task list which are interesting for me?

BW Housekeeping task list (see note http://service.sap.com/sap/support/notes/1829728).

1.17 When the original BW is decommissioned, the original delta queues should not be filled anymore. What is the advised method of deleting these delta queues?

The easiest way to decommission the original BW system is to stop all loading processes followed

by a deletion of source systems in the Administrator Workbench. The related delta queues of the

source systems have to be deleted in RSA7 manually.

1.18 Which applications do not support BW PCA? Those extractors that developed an own change pointer management which can only deliver one

single BW system will not be treated by BW PCA delta queue clone. That means those applications

have to check whether there is a workaround possible (e.g. duplication of the datasource, own logic,

etc.). The industry solution IS-H is such an example.

Please have a look at note 1932459 for unsupported datasources.

1.19 Customer wants to decommission a BW source system or reset the cloned delta queues created by BW PCA and restart the configuration. What are the required steps?

Suppose you have a BW source system connection from a source system A to a BW system B. For

this connection, delta is recorded. You want to delete the connection and the delta recording. There

are three cases to consider, for which we need to describe what happens in BW system B and BW

source system A when decommissioning the system.

1.19.1 Not even in source system A, an entry in table RSBASIDOC exists for BW system B

This is the case after delta queue cloning for PCA, when the new BW system B was not yet created

and connected to source system A.

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 6

You should copy the Z-Report attached to SAP note 2014906 to your source system A and execute

it, passing the logical system name of BW system B as input parameter.

This will cause the following changes in source system A:

1. delete the ALE change pointer delta recording in table TBDA2. Delta is no longer recorded for

those.

delete the delta datasources from RSA7 belonging to BW system B. Delta is no longer recorded for

those.

1.19.2 Within the BW system B, the source system A is visible in the Administrator Workbench.

In this case you have to delete the source system A from the administrator workbench in the source

system tree in BW system B.

This will cause the following changes in BW system B:

1. the entry for source system A in table RSBASIDOC will be deleted

2. all source system dependent metadata for system A will be deleted

This will cause the following changes in source system A:

1. the entry for BW system B in table RSBASIDOC will be deleted

2. all entries in table ROOSGEN for BW system B will be deleted

3. the ALE change pointer delta recording is set to inactive in table TBDA2. The delta is no

longer recorded for those. The entries of table TBDA2 are not deleted, as this is not required,

as delta is no longer recorded.

4. all delta datasources in RSA7 of source system A pointing to BW system B appear as red.

Nevertheless the delta is still recorded for those.

Therefore you have to copy the Z-report attached to SAP note 2014906 to your source system A

and execute it, passing system B as input parameter.

In the source system A following changes are caused by this report:

1. Delete the delta datasources from RSA7 belonging to BW system B. Delta is no longer

recorded for those.

1.19.3 Within the BW system B the source System A is not visible in the Administrator Workbench or does not exist in the metadata tables of BW system B. But in source system A, in table RSBASIDOC, the entry for connection towards BW system B is still present.

In this case you have to execute function module RSAP_BIW_DISCONNECT in single test in source

system A, passing the logical system name of BW system B as input parameter for the BW system,

and the logical system name of source system A as input parameter for the OLTP-system. Do also

set the FORCE_DELETE parameter to X.

This will cause the following changes in source system A:

2. the entry in table RSBASIDOC is deleted

3. all entries in table ROOSGEN for BW system B are deleted

4. the ALE change pointer delta recording is set to inactive in table TBDA2. The delta is no

longer recorded for those. The table entries are not deleted.

5. all delta datasources in RSA7 of source system A pointing to BW system B appear as red.

Nevertheless the delta is still recorded for those.

BW PCA FAQ – Questions related to BW Post Copy Automation

July 2015 7

Therefore you have to copy the Z-report attached to SAP note 2014906 to your source system A

and execute it, passing the logical system name of BW system B as input parameter.

In the source system A following changes are caused by this report:

1. Delete the delta datasources from RSA7 belonging to BW system B. Delta is no longer

recorded for those.

1.20 Useful reports We had a few customer situations in which the PCA procedure detected inconsistencies in already

existing queues in the ECC environment. As this leads to a stop in the whole PCA procedure until

the whole issue is fixed, we recommend to schedule the report RSC1_DIAGNOSIS in ECC, to check

the consistency of the queues which should be cloned.

www.sap.com/contactsap