overview bw system copy

1

WDEBU7 WorkshopChapter 02

Overview BW System CopyRoland Kramer - SAP Solutions Business Development, SAP EMEAVersion: October 2009

2

SAP AG 2006, BW Systemcopy, Roland Kramer / 2

SDN users please note the following

The Access of any material in the SAP community network and SAP developer network (SDN) is free of charge with your user login.

If you see any occurrence of “SAP Note” or “SAP Hinweis” and you want to access this Information, you have to logon to the SAP Marketplace (SMP) Note search which needs an additional login to the SMP. The login to SMP is depended to a valid customer contract and the S-user credentials.

Example for such a link: https://service.sap.com/sap/support/notes/

You can also add the Note Number directly at the end of the mentioned URL or go to New Note Search

3


System Copy with BW: Test System Upgrade

Simultaneous database copy to create upgrade test environment

upgrade Test

R3T

upgrade Test

BWT

TransportTransport

TransportTransport

BW

R/3

ALE / RFCALE / RFC

ConsolidationR3Q

ProductionR3P

DevelopmentR3D

DevelopmentBWD

ConsolidationBWQ

ProductionBWP

ALE / RFC

Logical system Names: The SAP Recommendation

BW source system ALE configuration: SAP source systems are identified via their logical system name (assigned to each client in SCC4)

Source systems identify BW via its logical system name

If all source system clients have the same logical system name, and all BW systems have the same logical system name (not recommended) , system copy is easy - just change server hostname in SM59

SM59 is the interface manager – this is where the RFC destinations are defined

Simultaneous copies of a pair of systems (BW, R/3) still preferable: datasource object consistency is guaranteed

copying R/3 only or BW only is possible without major effort – additional transports may be required to repair consistency.

4


“Refresh” of QA environment: simultaneous database copy

System Copy with BW: “Refresh” of QA Systems

TransportTransport

TransportTransportBW

R/3

ConsolidationR3Q

ProductionR3P

DevelopmentR3D

DevelopmentBWD

ConsolidationBWQ

ProductionBWP

ALE / RFCALE / RFC ALE / RFC

Non-unique Logical system Names: The “Gotchas”

Central User Administration Scenarios. Each system is uniquely identified by logical system name to CUA

CUA still possible with recommended landscape, but complex CUA configuration may be required.

Complex ALE scenarios in the system landscape (for example, central management of master data) may result in added complexities. Logical system names may need to be unique.

M:1 or 1:M source system connections:

If there are 2 or more R/3 system connected to 1 BW, the R/3 systems must have different logical system names.

If there are 2 or more BW systems connected to 1 R/3 system, the BW systems must have different logical system names.

5


R/3 “Refresh” without BW: Unique Logical Sys Names

If the pairs are not copied together, the procedure becomes more complex!

Changing the logical system name requires additional steps

Risk of data source inconsistencies

Possible deletion of data load processes

Refreshing the BW without simultaneously refreshing R/3 can be just as dangerous!

Logical system

Name:

“R3PCLT800”

Logical system

Name:

“BWPCLT300”

Logical system

Name:

“R3QCLT600”

Logical system

Name:

“R3DCLT400”

Logical system

Name:

“BWQCLT200”

Logical system

Name:

“BWDCLT100”

BW

R/3

ConsolidationR3Q

ProductionR3P

DevelopmentR3D

DevelopmentBWD

ConsolidationBWQ

ProductionBWP

ALE / RFCALE / RFC ALE / RFC

Tipps:

1. Avoid “refreshes” by maintaining strict controls within change management procedures

2. When copying BW systems, copy the source system's) simultaneously

3. When copying R/3 source systems, copy the related BW system at the same time

4. Non-unique logical system names make life easy, under certain conditions

5. Always backup systems before overwriting them

6. Carefully research and plan all aspects of the procedure prior to executing the refresh

6


Milestones of the System copy/UC Migration (771209)

Restore BW and Source Systems (RSA1)

Install DI with SAPInst based on Abap Export

Install CI with SAPInst

Create Abap Export with SAPInst

BDLS on BW and Source System

Post checks (RS_BW_POST_MIGRATION )

Migrate ODS-Objects (RSSGPCLA)

Pre checks (SMIGR_CREATE_DDL )

Follow up Actions in the Target System

UC Migration

UC Migration

Useful and additional Notes:

Note 886102: System Landscape Copy for SAP BW 2.X and 3.X

Note 885343: SAP System Landscape Copy (SAP BP Guide)

Note 793717: Client copy into the BW client in NetWeaver/mySAP ERP

Note 885441: Common Migration Errors

Note 790099: R/3 Parameter Settings for Unicode conversion

Note 888210: NW7.0: System copy (supplementary note)

Note 771209: NW04: System Copy (supplementary note)

Note 777024: BW3.0 and BW3.1 System Copy (supplementary note)

Note 733623: Oracle export/import for BW system copies

Note 771191: Copy BW objects to new tablespaces

Note 875986: Note Assistant: Important notes (SNOTE)

Note 936441: Oracle 9.2 settings for R3load based system copy

Note 928474: Error exporting the DDLOG package

Note 896023: Incorrect CREATE INDEX statement in DFACT.SQL

Note 942540: System copy fails on SAPDFACT import

Note 898358: R3load: Entries in "/MAXDB/INDEXSTATEMENTS" are kept

Note 901592: Inconsistent change log tables after migration

Note 849857: Potential data loss in PSA/change log

Note 856097: Check and repair program for Note 849857

7


Note 1333302 - Special procedure for BW system copy

8


Useful Documents and Notes

This Documents gives you an Overview how to proceed with BI System Copies.

It can be found under http://service.sap.com/bi Service & Implemen-tation How Toorhttp://help.sap.comSAP Best Practices

Check also the Best Practice Guide available at http://service.sap.com/solutionmanagerbp

Notes for the SAP BW system copy and CTS (maybe outdated or replaced):

184754 Procedure for the BW database copy

325525 Copying and renaming systems in a BW environment

121163 BDLS: logical source system names

122679 You may only work in client XXX. Brain 009

116520 Installation / copying client 000 in the BW System

127326 CTS for InfoSources, Update Rules, etc.

184586 System changeability and BW

184971 Notes on BW source system connections

140276 Error when connecting source systems

544509 ALE: Converting the name of the "logical system"

543715 Pilot Projects for migrations and system copies

Other Notes for the NT/I386 Environment:

147243 DB-copy Scenario for NT/I386 systems

142100 New SAP Service with 4.5B

122814 Authorization problems during the NT Migration Oracle 8.x

117395 Authorization problems for file I/O on Windows NT

Note that for the BW 3.5 (Basis 6.40) the pilot project status is not needed anymore.See Note 771209 for more Details

9


http://service.sap.com/instguidesNW04 (Oracle)

As of SAP Web AS 6.40 SR 1, the new OraBRCopy Java tool replaces the former R3COPY shell script.

It works on Unix and Windows as well. The tool generates a file CONTROL.SQL into the current working directory, which can be used without further adaptations on the target system.

10


Oracle specific Procedure (OraBrCopy)

New with Basis 6.40 the tool OraBRCopy replaces the old R3copy tool. See the Documentation OraBRCopy.pdf in the file ORABRCOPY.SAR

11


Some Remarks Regarding ”Copied Systems“ (Oracle)

If you created a system for testing the SAP BW upgrade based on a system copy, make sure you check the following before starting the upgrade: After the system copy has been created, run the scripts catalog and

catproc as sysadmin for the consistency of the Oracle database; also run the sapdba_role script.

If your start release of SAP BW is version 2.x AND you already make use of the temporary, locally managed PSAPTEMP2, the data file(s) will not be recognized by the new database any more. You will need to create a new temporary data file, otherwise you will get an error message like: ”ORA-25153 Temporary table space is Empty?“. Make sure, you have enough space left.

You can also check the existence of the data file with ST04 => Detailed => V$tables => V$TEMPFILES.

After the “normal procedure“ proceed with transaction BDLS to adjust the IDocs to the new system.

In transaction RSA1 run ”Restore Source system“ under the section ”Source systems.“

Check with WE20 if the Partner Profiles are maintained correctly.

Refer also to the section „restore of source systems“

See also Note 416772

The temporary tablespace (tempsize) should be at least twice the size of the largest DB index.

More Notes to consider/apply:

Note 899966: Oracle: Error in homogeneous migration, primary index missing

Note 925309 Oracle: Problems in homogeneous migration

Note 931333: Single indexes on dimension tables after system migration

Note 948780 - Incorrect indexes in ABAP Dictionary after post-migration

Note 830965 - VBDATA, DDLOG: size and increase in size

12


BW System Copy – Technical Related Checks

Make sure you provide enough space in the file system if you have not created a locally managed temporary table space (PSAPTEMP) yet. When the table space is created, Oracle is not allocating the space on the file system directly. It will be used dynamically due to the table space type. (Example)

CREATE TEMPORARY TABLESPACE PSAPTEMP

TEMPFILE '/oracle/<SID>/sapdataX/temp_1/temp.data1' size 10000M

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M;

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP";

If there was a locally managed PSAPTEMP already, you can also reassign the existing table space.

ALTER TABLESPACE PSAPTEMP add

TEMPFILE'/oracle/<SID>/sapdataX/temp_1/temp.data1' size 10000M

reuse EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M autoextend off

tablespace types:

As of Oracle 8.1.7, there are exactly the following four types of table spaces as regards the extent management and tablespace content:

(1) Dictionary permanent USER (INITIAL, NEXT, ...)

(2) Dictionary temporary USER (INITIAL, NEXT, ...)

(3) Locally permanent UNIFORM or system (AUTOALLOCATE)

(4) Locally temporary UNIFORM

Up to Oracle 8.1.7, the default for EXTENT MANAGEMENT was always DICTIONARY (except for type (4)).

A "TEMPORARY tablespace" (type 4) is always(!) "LOCAL UNIFORM".

A "tablespace ... TEMPORARY" (type 2) is always(!) "DICTIONARY".

A "LOCAL AUTOALLOCATE" tablespace (type 3) is always(!) "PERMANENT".

In the Oracle data Dictionary, you can find:

- datafiles (for types 1,2,3) in DBA_data_files and V$datafile,

- TEMPFILES (for type 4) in DBA_TEMP_FILES and V$TEMPFILE.

13


Check with SE14 for invalid (Temp) Tables

Check also carefully the Notes section for additional cleanup

More Additional Checks:

Run the Program SAP_DROP_TMPTABLES, and check regularly the latest Notes for this Program, like Note 883843 and 974639 and 1106393!

Check also for Table DBDIFF the Function Module RSDDTMPTAB_CLEANUP with I_NAMETYPE='01' to ’06’ (Temp Präfixes) ONLY for cleanup old temporary table entries. In conjunction you can also use the Program SAP_UPDATE_DBDIFF to clean the table DBDIFF. You may run /$sync before. See also Note 1035373.

Check the Table RSDD_TMPNM_ADM (see Note 811354 for details)

- select count (*) from <schema-id>. RSDD_TMPNM_ADM where nametype = '06‘;delete from <schema-id>. RSDD_TMPNM_ADM where nametype = '06' and free = 'X‘;

- select count (*) from <schema-id>. RSDD_TMPNM_ADM where nametype = '01‘delete from <schema-id>. RSDD_TMPNM_ADM where nametype = '01' and free = 'X'

Use the Program RSRA_CLUSTER_TABLE_REORG to clean entries in Table RSIXWWW. See Note 589899 for more details.

Details from Note 883843 and 974639 to clean Nametab entries (the latest Version for SAP_DROP_TMPTABLES may also clean this Nametab entries):

- select count (*) from <schema-id>.ddntt where tabname like '/BI0/03%';

- DELETE FROM <schema-id>.DDNTT WHERE TABNAME LIKE '/BI0/03%';

- select count (*) from <schema-id>.ddntf where tabname like '/BI0/03%';

- DELETE FROM <schema-id>.DDNTF WHERE TABNAME LIKE '/BI0/03%';

Alternatively, you may use report RS_NAMT_CLEAR described in note 152420 (Note 1051132!)

In Advance you may also truncate tables DDLOG and DBTABLOG before upgrade.

14


Run the Report SMIGR_CREATE_DDL before Export

More Additional Checks - continued:

Report RSAR_PSA_PARTITION_CHECK (Note 1042182)

Report SAP_PSA_PARTNO_CORRECT and RSAR_PSA_CLEANUP_DIRECTORY (Note 1102626)

On Unix please make sure that the Export directory has enough rights for writing the DDL scripts directly to the directory.

For System Copy on Oracle you may create space statistics beforehand, seeNote 554031 - Creating space statistics with BRCONNECT

brconnect -u / -c -f stats -o SAP<SID> -t all -m +I -s P10 -f allsel,collect,method,precision,keep -p 4

If you encounter Problems with the import of some F-Tables with to much partitions like described in Note 590370 then you have to modify the script DFACT.SQL created with SMIGR_CREATE_DDL. The Solution from Note 859585 will not solve the Problem.

(DB) INFO: /BIC/FGLBGMISTK~04 created #20060504021239DbSl Trace: Error in exec_immediate()DbSl Trace: ORA-14020 occurred when executing SQL statement (parse error offset=148)(DB) ERROR: DDL statement failed

this is known issue which is caused by a wrong behavior of the SMIGR_CREATE_DDL report.

To correct this remove the 'ENDEXEC.' entries within the 'alter table‘ statements of '/BI0/F0BWTC_C06' by ';‘ in the script DFACT.SQL and retry the Installation.

15


Get the latest Version of the Split tools, Note 784118

Package and Table Splitter (SPLIT)

Splitting packages is only available for release 4.0B and above.

Splitting tables is only available on project basis for release 6.20 and above.

The Splitter tool can be used for splitting the following:

STR/EXT files

6.40: TSK files with WHERE clauses (including an adaptation of the corresponding STR/EXT files)

7.00: WHR files with WHERE clauses (including an adaptation of the corresponding STR/EXT files)

CAUTION:

Please pay attention to note 833946, if you use the Splitter from the NW 04 or NW 04 SR1 installation kit or version 1 from the SAP service marketplace.

When you split the R3load-STR files, a separate package is created for the DDLOG table. When this package is exported, the R3load terminates with the following error message: (TSK) ERROR: file <Installation directory>/DDLOG.TSK is empty

The problem is eliminated with

the archives of the installation master DVD of NetWeaver 7.0 SR1

Patch 2 of the MIGMON.SAR archive for Version 7.0 on the SAP Service Marketplace

Note that you can always use the latest Version of the SPLIT tools (Basis 7.00)

Note 855772: New Distribution Monitor Version 1.4.0

Latest nw04 Installer can be found:Installations and Upgrades" SAP Technology Components" SAPINST" SAPINST 640 ERP04_PRC

16


Use the SAPInst tool for the Abap Export

Suggested Start Levels for the Systemcopy with export/import:

Note Basis SP-Level (former) SP-Level (new)

777024 620 SAP_BASIS 46 SAP_BASIS 58



One of the main reason for that is the fact, that some of the correction notes for the report SMIGR_CREATE_DDL cannot be implemented before Basis 620/55 or Basis 640/14 or not available before the new mentioned SP-Level.Note 931333 for the latest correction for SMIGR_CREATE_DDL is even based on 640/17.

Note 948780 - Incorrect indexes in ABAP Dictionary after post-migration

17


Check the right Character Set

Single code page Unicode

18


Choose your Target DB Version and JRE Directory

19


Choose the right Codepage for Export

1100 single code page 4103 little endian 4102 big endian

Note 552464: What is Big Endian / Little Endian? What Endian do I have?

Big Endian:

the most significant byte is stored in memory at the lowest address, and the least significant byte at the highest address. (The big end comes first.) As an analogy, we say "twenty-four" in English; the more significant number, twenty, comes first.This is also called most significant byte (MSB) ordering.4102 Big EndianIBM 390, AS/400, PowerPC (AIX), Linux on zSeries (S/390), Linux on Power, Solaris_SPARC, HP PA-RISC, Itanium (HP-UX)

Little Endian:

the least significant byte of the number is stored in memory at the lowest address, and the most significant byte at the highest address. (The little end comes first.) As an analogy, we say "fourteen" in English; the less significant number, four, comes first.This is also called least significant byte (LSB) ordering.4103 Little EndianAlpha, Intel X86 (and clones), X86_64, Itanium (Windows + Linux), Solaris_X86_64

20

Import Abap Export as new DI with SAPInst

21


Choose the directory where to copy the Abap export

22


Provide enough Space in the Target System

If your Unix System already supporting JFS-2 you can already choose File sizes up to 32 GB depending also on the Backup software

Note that not always you gain space with the export/import Procedure. You will definitely Reorg the data with the fresh Installation.

With the MaxDB Installation the necessary DB size is shown on the top of the screen

23


Check the PSAPTEMP settings (TEMPORARY!)

24


Check the Tablespace settings

25


Check Load Import Parameter (correct Codepage)

1100 single code page 4103 little endian 4102 big endian

26


Check Database user (outln, dbsnmp)

27


Post Activities Following the SAP System Copy Creation

Run transaction BDLS for all systems. Note that the new logical source system names must not be in table TBDLS. Check this with BD54. The BDLS transaction only converts the IDOCS. To complete the tasks, you will also have to restore the systems (BW and R/3) in the AWB.

Check both, the SAP BW system and the source systems (R/3) and restore the connections in the AWB using RSA1.

To restore the source systems, check Note 184322 and delete the assignment for the SAP BW system in the SAP R/3 system with the function module RSAP_BIW_DISCONNECT_40_20.See the additional chapter “Restoring source systems.”

Run the Program RS_BW_POST_MIGRATION

Check the partner profiles in WE20 for the systems.

Check IDoc ports in WE21 for the systems.

Check the IDoc type in WE30 for the systems.

Differences to the BW system copy:

Basically there are only two things to do after the system copy is fulfilled.

transaction BDLS changes the IDocs to the new logical Source system Name

Restore Source system in RSA1 changes the DataSources and the assignment inside the Administrator Workbench.

More Details for restoring the Source system can be found in the Chapter „Restoring of Source systems“

Note 524554: Storing destinations in the BW environment

Note 742009: ALE: BDLS for fields in the /xxx/ namespace dump

Note 110849: "Error during insert in port table" (create source system)

Note 1000062: 70SP13: Conversion of logical system names

Corrections of the Program RS_BW_POST_MIGRATION after SPS 15:

Note 884124: Cube activation terminates after heterogeneous system migration

Note 933610: Heterogeneous system migration follow-on for Note 884124

Note 948780: useless Indexes after Post migration in DDIC

Note 901592: Inconsistent change log tables after migration

Note 900961: Post processing non-cumulative InfoCubes in Program RS_BW_POST_

Note 906090: Inconsistent non-cumulative cubes after heterogeneous system

28


How to Proceed Note 184322 replaced by 886102

Check Note 184322 Run transaction BDLS in the SAP BW target system to create the

new logical system. Note that the new definition must not be in the table TBDLS (transaction BD54). Note 1000062 - 70SP13: Conversion of logical system names

Go to the SAP R/3 source system and use RSAP_BIW_DISCONNECT_40_20 with SE37 and delete the existing SAP R/3 connection to the respective SAP BW System.

Go to SM59 in the SAP BW target system, create the new RFC connection and remove the old connection.

Go to WE20 in the SAP BW target system an delete the existing partner definition.

Go to the SAP BW target system and use transaction RSA1 Source system and restore the desired SAP R/3 source system.

Check the protocol of the recreation in the SAP BW system.

29


Running the Conversion of Log. sys. Names with BDLS

Note that the new logicalsource system namemust not be in tableTBDLS.

Further notes:

The conversion of the logical system name has far-reaching consequences. Therefore, we recommend that you contact an SAP consultant before starting it. The following points should be observed:

In productive systems the conversion of the logical system name is not provided. The reason is that the relevant database tables are dynamically determined by certain domains (LOGSYS and EDI_PARNUM). If there are applications where the tables do not reference these domains, the data are not converted. Another reason is that certain data could be saved as part of fields in cluster or pool tables with regard to the logical system. Such data are not converted.

During the run of the conversion report, no other activities may be carried out in the system.

All IDocs in the system must be processed beforehand since the logical system name could be contained in the IDoc data record. The logical system name in IDoc data records would not be taken into account for conversion.

The conversion is carried out in the current client. Therefore, the process must also be carried out in all partner systems.

If the new logical system name already exists in the system, it can cause errors for tables in which the logical system is key field or unique index (for example, COFIO1). In this case the number of converted entries is smaller than the number of selected entries. Manual post processing must be carried out in this case, and if necessary the conversion must be started again.

The conversion report that was dynamically generated from Report RBDLSMAP (up to SAP Release 6.10) can also be run in the background, if the corresponding input fields are filled with values. In this case, all confirmation prompts are automatically confirmed with Yes during the run; on the other hand, user interaction is required in the online execution. You must pay attention to this during the conversion itself.

If a termination occurs due to the database roll area, you should either restart the roll area as high as possible or reduce the parameter 'Number of entries per commit' from the default value. In order to gain performance, this parameter should be as great as possible.

After successfully completing the conversion, synchronize the table buffers in the server.

Export the list of conversion results (on the screen) to a local file for test purposes.

30


Action on the SAP R/3 Source System

This Function Modules are imported into R/3 based SAP System with the R/3 Plug In Module.

With that Function Module you can delete Entries out of the Table RSBISIDOC which is protected against changing in SE16. It is strictly recommended only to use the mentioned Function Modules to modify the Entries otherwise you can permanently destroy a working BW System.

31


Deleting the Existing RFC Connection in BW with SM59

If the old Entries are not removed the reconnecting Process always tries to restore this connection again.

If the Process fails you should remove the „_DIALOG“ connection before you try to reconnect again, due the Fact that when you copy SM59 connections the Password will not be copied.

An Alternative would also to use trusted System connection. Therefore you don‘t have to deal with Passwords again. See Note 128447 and 1167901 for Details.

32


Deleting/Checking the Partner Profile in BW with WE20

33


Checking IDoc Ports and Types with WE21 and WE30

The restoring process take care of all Settings inside the ALE configuration. It is not necessary to use more transactions as

WE20 Partner Profiles

WE21 IDOC Ports

WE30 IDOC Types

34


Restoring the Source System in BW with RSA1

The restore Process takes care of all ALE related Settings. No additional Customizing is necessary.

More additional Notes:

Note 126066: Add source system: Message R3220

Note 150315: BW-Authorizations for Remote-User in BW and OLTP

Note 538052: Maintenance of Myself destination in BW

Note 110849: "Error during insert in port table" (create source system)

Note 522653: Source system connection tool Transaction RS_LOGSYS_CHECK

35


Maintaining Suggestions for the Extraction Users in BW

When you are using different Users for the connection or users different from the Default you can change the Names at any time.

Note that when you call one of these Transaction out of Transaction RSA1 (Administrator Workbench) you have also to close the RSA1 also, because during the call of the Transaction some Table will be buffered.

If you are planning to replace the existing User with a new User, please make sure that you first restore the connection with the old user before you try to restore the Connection with another User.

If you encounter Messages like RS3220 please Consult the Note 126066

Note 538052: Maintenance of Myself destination in BW

S_BI-WX_RFC to call the source system (R/3 or BW)

S_BI-WHM_RFC call the BW

36


Prerequisites for the System Change Option

Note that for a successful source system connection, the following are required for the system change option: SCC4 client maintenance

Changes to repository and cross-client customizing allowed

Automatic recording of changes

CATT and eCATT are allowed

SE06 namespaces Customer namespace modifiable

Customer developments HOME modifiable

Local developments (no automatic transport) LOCAL modifiable

Business Warehouse SAP name space /BI0/ modifiable

Business Warehouse Customer name space /BIC/ modifiable

When you connect productive R/3 and ERP systems to the productive SAP BW system, note that will have to open the systems during the connection. Afterwards you can close it again. No changes will be done afterwards.

As a rule, no system changes are permitted in productive systems at all. Connecting a system as a source system to a BW or connecting a BW to a new source system will, however, mean changes as far as the system change option is concerned. You will have therefore made sure that the following changes are permissible in the relevant clients of the system when you connect the source system.

Cross-client Customizing and Repository changesIn the BW Customizing Implementation Guide, select the relevant client under Business Information Warehouse Connections to Other Systems General Connection Settings Assign Logical System to Client, then choose Goto Detail. Choose the entry Changes to Repository and Cross-Client Customizing Permitted in the field Changes to Cross-Client Objects.In the source system, make this setting in the Implementation Guide under Cross-application Components Distribution (ALE) Basic Settings Set Up Logical System Assign Logical System to Client.

Changes to the software components local developments and Business Information Warehouse.You can set up the changeability with Transaction SE03 (Organizer Tools). Choose Organizer Tools Administration Set Up System Change Option, then Execute. Make the settings in the subsequent screen.

Changes in the customer name areaAgain, you can set up the changeability for the customer name area with Transaction SE03.

Changes to BW namespaces /BIC/ and /BI0/Again, you can set up the changeability of the BW namespace with Transaction SE03.

37


Settings in SE06

38


Checking the Protocol

To call the Application Log directly you can call this with Transaction SLG1

With Transaction SLG2 you can administrate the Application log, e.g. Delete old logs to save Disk space and get better Performance.

39


Checking the Source System Afterwards

40


Checklist for Connecting BW - R/3

ChecklistChecklist where, whatwhere, what

Define user <SID>_ALEBW in BW and R/3 R/3, BW SU01(Make sure you have the right permissions)

Define logical system names (<SID>CLNT<client>) R/3, BW BD54

(Check ALE communication) R/3, BW SALE)

Check RFC connection (with remote Logon) R/3, BW SM59

Check the system settings before you connect them R/3, BW SCC4, SE06

Define the new source system (manually) BW RSA1 (This is automatically starting a meta data upload)

Customizing settings from the R/3 system R/3, BW SBIW(Do this before the first data load starts)

Check/Transfer of global settings R/3, BW RSA1(Use this function as a simulation to check)

Activate the necessary BC data sources R/3, BW SBIW, RSA1

Perform the meta data upload on the BW system R/3, BW SBIW, RSA1

Creating an SAP source system manually

In the initial screen of the source system choose Tools Administration Maintain Users Users and create a background user with a password and the authorization profile S_BI-WX_RFC.

Define the RFC destination parameters for the SAP source system in BW. To do this, choose Tools Administration Management Network RFC Destinations in BW.The destination name must correspond to the logical name of the source system that you entered for the process step Maintain Logical System in the implementation guide of the source system. For user and password, enter the background user that you created in step 1.

Define the RFC destination parameters for the SAP Business Information Warehouse in the source system. Select Tools Administration Management Network RFC Destinations here in the source system. Enter the information on the server name previously taken from the source system.The destination name must correspond to the logical name of the BW system that you entered for BW Customizing Implementation Guide in the process step Name Logical System. ALE communicates with the help of the SAP Business Information Warehouse name that you defined. The defined name, therefore, represents an identification of the SAP Business Information Warehouse.For the user and password, enter the background user that you defined in the BW Customizing Implementation Guide under Business Information Warehouse Connections to other Systems Connection between SAP Systems and BW.

41


Run Program RS_BW_POST_MIGRATION after Import

Invalidate Generated Programreset timestamps to regenerate all generated programs

Adapt DBDIFF to New DBMaintain exception table containing differences between Data Dictionary and DB Other Work

only relevant for DB6 databases

Adapt Aggregate IndexesIndex Definition is checked and aligned for Aggregates

Adapt Basis Cube IndexesIndex Definition is checked and aligned for Cubes

Generate New PSA Versionthis generates new PSA versions and only for this the source system connection must be available uses report rs_transtru_activate_all

Delete Temporary Tablesas mentioned

Repair Fact Viewrecreate Fact Views for InfoCubes (SAP_FACTVIEWS_RECREATE)

Restriction to One Cubeas mentioned

Other Workas mentioned

According to Note 771209 you should run the Report with the Variant POSTMGR. These contains the following Options:

Other Work X

Delete Temporary Tables X

Repair Fact View X

42


ODS object - SYSTEMCOPY, migration (RSSGPCLA)

Additions to the Transaction RSSGPCLA:

You may also run the Program RSSM_OLTP_INIT_DELTA_UPDATE for R/3 source systems, see Notes 591382 and 424848 for more details. This is needed if the BW System was copied with out copying the connected R/3 based System. The Program synchronizes the delta Marker.

For ODS Objects from BW system, check with Note 518426 and use the Transaction RSSGPCLA. This is needed also, if the BW System is a source of other BW Systems.

Run the Program RSAR_PSA_CLEANUP_DIRECTORY from Note 849857 to prevent potential data loss in PSA/change log and the Program SAP_PSA_ZEROCORRECT from Note 856097 in case of Problems with Partition 0

Note 1051664 - Check and repair program BW7.x for Note 849857

43


Copyright 2008 SAP AG All rights reservedNo 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.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.