WDEBU7 Workshop Chapter 02 Overview BW System Copy

Roland Kramer - SAP Solutions Business Development, SAP EMEA Version: October 2009

1

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

 SAP AG 2006, BW Systemcopy, Roland Kramer / 2

2

System Copy with BW: Test System Upgrade

upgrade Test BWT

Development BWD

Consolidation BWQ

Production BWP

BW
Transport Transport

ALE / RFC

ALE / RFC

ALE / RFC

R/3
upgrade Test R3T Development R3D

Transport

Transport

Consolidation R3Q

Production R3P

Simultaneous database copy to create upgrade test environment
 SAP AG 2006, BW Systemcopy, Roland Kramer / 3

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.

  

3

System Copy with BW: “Refresh” of QA Systems

Development BWD

Consolidation BWQ

Production BWP

BW

Transport

Transport

ALE / RFC

ALE / RFC

ALE / RFC

Transport

Transport

R/3
Development R3D Consolidation R3Q Production R3P

“Refresh” of QA environment: simultaneous database copy
 SAP AG 2006, BW Systemcopy, Roland Kramer / 4

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.

  

4

the procedure becomes more complex! Changing the logical system name requires additional steps Risk of data source inconsistencies BW ALE / RFC ALE / RFC ALE / RFC Possible deletion of data load processes Refreshing the BW without simultaneously refreshing R/3 can be just as dangerous! R/3 Development R3D Logical system Name: “R3DCLT400” Consolidation R3Q Logical system Name: “R3QCLT600” Production R3P Logical system Name: “R3PCLT800”  SAP AG 2006. Avoid “refreshes” by maintaining strict controls within change management procedures 2. under certain conditions 5. Roland Kramer / 5 Tipps: 1. When copying R/3 source systems. Non-unique logical system names make life easy. copy the related BW system at the same time 4. Carefully research and plan all aspects of the procedure prior to executing the refresh 5 .R/3 “Refresh” without BW: Unique Logical Sys Names Logical system Name: “BWDCLT100” Development BWD Logical system Name: “BWQCLT200” Consolidation BWQ Logical system Name: “BWPCLT300” Production BWP If the pairs are not copied together. copy the source system's) simultaneously 3. When copying BW systems. BW Systemcopy. Always backup systems before overwriting them 6.

Milestones of the System copy/UC Migration (771209) Pre checks (SMIGR_CREATE_DDL ) Create Abap Export with SAPInst Install CI with SAPInst Install DI with SAPInst based on Abap Export BDLS on BW and Source System Restore BW and Source Systems (RSA1) Post checks (RS_BW_POST_MIGRATION ) Migrate ODS-Objects (RSSGPCLA) Follow up Actions in the Target System  SAP AG 2006.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               6 .2 settings for R3load based system copy Note 928474: Error exporting the DDLOG package Note 896023: Incorrect CREATE INDEX statement in DFACT.0 and BW3. BW Systemcopy.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. Roland Kramer / 6 UC Migration UC Migration Useful and additional Notes:      Note 886102: System Landscape Copy for SAP BW 2.X and 3.0: System copy (supplementary note) Note 771209: NW04: System Copy (supplementary note) Note 777024: 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.

Roland Kramer / 7 7 .Note 1333302 .Special procedure for BW system copy  SAP AG 2006. BW Systemcopy.

sap.sap.com  SAP Best Practices  Check also the Best Practice Guide available at http://service.5B Authorization problems during the NT Migration Oracle 8.sap.Useful Documents and Notes  This Documents gives you an Overview how to proceed with BI System Copies.com/ solutionmanagerbp  SAP AG 2006. Update Rules.x Authorization problems for file I/O on Windows NT Other Notes for the NT/I386 Environment:  142100  122814  117395  Note that for the BW 3. Roland Kramer / 8 Notes for the SAP BW system copy and CTS (maybe outdated or replaced):  184754  325525  121163  122679  116520  127326  184586  184971  140276  544509  543715  147243 Procedure for the BW database copy Copying and renaming systems in a BW environment BDLS: logical source system names You may only work in client XXX. etc.5 (Basis 6.com/bi  Service & Implementation  How To or http://help. System changeability and BW Notes on BW source system connections Error when connecting source systems ALE: Converting the name of the "logical system" Pilot Projects for migrations and system copies DB-copy Scenario for NT/I386 systems New SAP Service with 4.40) the pilot project status is not needed anymore. See Note 771209 for more Details 8 . BW Systemcopy. Brain 009 Installation / copying client 000 in the BW System CTS for InfoSources.  It can be found under http://service.

 SAP AG 2006.SQL into the current working directory.  It works on Unix and Windows as well. The tool generates a file CONTROL. which can be used without further adaptations on the target system.40 SR 1. BW Systemcopy.sap. Roland Kramer / 9 9 .com/instguidesNW04 (Oracle)  As of SAP Web AS 6. the new OraBRCopy Java tool replaces the former R3COPY shell script.http://service.

40 the tool OraBRCopy replaces the old R3copy tool.pdf in the file ORABRCOPY.Oracle specific Procedure (OraBrCopy)  New with Basis 6. BW Systemcopy. Roland Kramer / 10 10 .SAR  SAP AG 2006. See the Documentation OraBRCopy.

More Notes to consider/apply:      Note 899966: Oracle: Error in homogeneous migration.VBDATA. run the scripts catalog and catproc as sysadmin for the consistency of the Oracle database.x AND you already make use of the temporary.     After the “normal procedure“ proceed with transaction BDLS to adjust the IDocs to the new system. DDLOG: size and increase in size 11 . also run the sapdba_role script.“ Check with WE20 if the Partner Profiles are maintained correctly. If your start release of SAP BW is version 2. primary index missing Note 925309 Oracle: Problems in homogeneous migration Note 931333: Single indexes on dimension tables after system migration Note 948780 . Make sure. BW Systemcopy. locally managed PSAPTEMP2. you have enough space left. the data file(s) will not be recognized by the new database any more.Incorrect indexes in ABAP Dictionary after post-migration Note 830965 .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. otherwise you will get an error message like: ”ORA-25153 Temporary table space is Empty?“. In transaction RSA1 run ”Restore Source system“ under the section ”Source systems.  SAP AG 2006. You will need to create a new temporary data file. Roland Kramer / 11    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. You can also check the existence of the data file with ST04 => Detailed => V$tables => V$TEMPFILES.

 ALTER TABLESPACE PSAPTEMP add TEMPFILE'/oracle/<SID>/sapdataX/temp_1/temp. (Example) CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE '/oracle/<SID>/sapdataX/temp_1/temp. . TEMPORARY" (type 4) is always(!) "LOCAL UNIFORM".. BW Systemcopy. NEXT. When the table space is created. A "TEMPORARY tablespace" A "tablespace . NEXT.) UNIFORM or system (AUTOALLOCATE) UNIFORM  Up to Oracle 8. Oracle is not allocating the space on the file system directly.data1' size 10000M reuse EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M autoextend off  SAP AG 2006.) USER (INITIAL. (type 2) is always(!) "DICTIONARY".  In the Oracle data Dictionary..7.. the default for EXTENT MANAGEMENT was always DICTIONARY (except for type (4)).1.7..3) in DBA_data_files and V$datafile.2.. you can find: . A "LOCAL AUTOALLOCATE" tablespace (type 3) is always(!) "PERMANENT". you can also reassign the existing table space.datafiles (for types 1. . there are exactly the following four types of table spaces as regards the extent management and tablespace content: (1) Dictionary (2) Dictionary (3) Locally (4) Locally permanent temporary permanent temporary USER (INITIAL. .  If there was a locally managed PSAPTEMP already.data1' size 10000M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M.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. It will be used dynamically due to the table space type. Roland Kramer / 12 tablespace types:  As of Oracle 8..1.TEMPFILES (for type 4) in DBA_TEMP_FILES and V$TEMPFILE. 12 . ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP".

delete from <schema-id>.select count (*) from <schema-id>.  Check the Table RSDD_TMPNM_ADM (see Note 811354 for details) . Roland Kramer / 13 More Additional Checks:  Run the Program SAP_DROP_TMPTABLES. 13 .select count (*) from <schema-id>. .DDNTT WHERE TABNAME LIKE '/BI0/03%'. You may run /$sync before. RSDD_TMPNM_ADM where nametype = '06‘.select count (*) from <schema-id>.  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.  Details from Note 883843 and 974639 to clean Nametab entries (the latest Version for SAP_DROP_TMPTABLES may also clean this Nametab entries): . .Check with SE14 for invalid (Temp) Tables  Check also carefully the Notes section for additional cleanup  SAP AG 2006. See Note 589899 for more details.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. and check regularly the latest Notes for this Program. BW Systemcopy. RSDD_TMPNM_ADM where nametype = '06' and free = 'X‘.DELETE FROM <schema-id>. 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.ddntt where tabname like '/BI0/03%'. See also Note 1035373. . RSDD_TMPNM_ADM where nametype = '01‘ delete from <schema-id>.DDNTF WHERE TABNAME LIKE '/BI0/03%'.ddntf where tabname like '/BI0/03%'. In conjunction you can also use the Program SAP_UPDATE_DBDIFF to clean the table DBDIFF.select count (*) from <schema-id>. .

14 . see Note 554031 .collect.Run the Report SMIGR_CREATE_DDL before Export  SAP AG 2006. BW Systemcopy.method.SQL and retry the Installation.  To correct this remove the 'ENDEXEC. The Solution from Note 859585 will not solve the Problem.‘ in the script DFACT. Roland Kramer / 14 More Additional Checks .Creating space statistics with BRCONNECT  brconnect -u / -c -f stats -o SAP<SID> -t all -m +I -s P10 -f allsel.SQL created with SMIGR_CREATE_DDL.' entries within the 'alter table‘ statements of '/BI0/F0BWTC_C06' by '. For System Copy on Oracle you may create space statistics beforehand.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.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.  (DB) INFO: /BIC/FGLBGMISTK~04 created #20060504021239 DbSl 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.

0B and above.0 on the SAP Service Marketplace STR/EXT files   CAUTION:       Note that you can always use the latest Version of the SPLIT tools (Basis 7. a separate package is created for the DDLOG table.00) Note 855772: New Distribution Monitor Version 1.TSK is empty The problem is eliminated with  the archives of the installation master DVD of NetWeaver 7.SAR archive for Version 7.Get the latest Version of the Split tools. The Splitter tool can be used for splitting the following: 6. BW Systemcopy. When you split the R3load-STR files. Roland Kramer / 15 Package and Table Splitter (SPLIT)    Splitting packages is only available for release 4.00: WHR files with WHERE clauses (including an adaptation of the corresponding STR/EXT files) Please pay attention to note 833946.0 SR1  Patch 2 of the MIGMON. Note 784118  SAP AG 2006.0 Latest nw04 Installer can be found: Installations and Upgrades" SAP Technology Components" SAPINST" SAPINST 640 ERP04_PRC 15 . When this package is exported.20 and above. the R3load terminates with the following error message: (TSK) ERROR: file <Installation directory>/DDLOG. Splitting tables is only available on project basis for release 6.4. if you use the Splitter from the NW 04 or NW 04 SR1 installation kit or version 1 from the SAP service marketplace.40: TSK files with WHERE clauses (including an adaptation of the corresponding STR/EXT files) 7.

Note 948780 . Roland Kramer / 16 Suggested Start Levels for the Systemcopy with export/import:     Note 777024 771209 888210 Basis SP-Level (former) SP-Level (new) 620 640 700 SAP_BASIS 46 SAP_BASIS 10 SAP_BASIS 00 SAP_BASIS 58 SAP_BASIS 16 SAP_BASIS 07  One of the main reason for that is the fact.Use the SAPInst tool for the Abap Export  SAP AG 2006. BW Systemcopy. Note 931333 for the latest correction for SMIGR_CREATE_DDL is even based on 640/17.Incorrect indexes in ABAP Dictionary after post-migration  16 . 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.

Check the right Character Set  Single code page  Unicode  SAP AG 2006. Roland Kramer / 17 17 . BW Systemcopy.

BW Systemcopy.Choose your Target DB Version and JRE Directory  SAP AG 2006. Roland Kramer / 18 18 .

(The little end comes first. Roland Kramer / 19  Note 552464: What is Big Endian / Little Endian? What Endian do I have? the most significant byte is stored in memory at the lowest address. Linux on Power. and the least significant byte at the highest address. 4102 Big Endian IBM 390. Solaris_SPARC. Itanium (HP-UX) the least significant byte of the number is stored in memory at the lowest address. we say "twenty-four" in English. X86_64. Solaris_X86_64 Big Endian:  Little Endian:  19 . This is also called most significant byte (MSB) ordering. comes first.) As an analogy. Linux on zSeries (S/390). comes first.) As an analogy. Itanium (Windows + Linux). Intel X86 (and clones). four. twenty. (The big end comes first. and the most significant byte at the highest address.Choose the right Codepage for Export  1100 single code page  4103 little endian  4102 big endian  SAP AG 2006. PowerPC (AIX). HP PA-RISC. This is also called least significant byte (LSB) ordering. 4103 Little Endian Alpha. AS/400. we say "fourteen" in English. BW Systemcopy. the more significant number. the less significant number.

Import Abap Export as new DI with SAPInst 20 .

BW Systemcopy.Choose the directory where to copy the Abap export  SAP AG 2006. Roland Kramer / 21 21 .

Roland Kramer / 22    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.Provide enough Space in the Target System  SAP AG 2006. BW Systemcopy. With the MaxDB Installation the necessary DB size is shown on the top of the screen 22 . You will definitely Reorg the data with the fresh Installation.

Check the PSAPTEMP settings (TEMPORARY!)  SAP AG 2006. Roland Kramer / 23 23 . BW Systemcopy.

Roland Kramer / 24 24 . BW Systemcopy.Check the Tablespace settings  SAP AG 2006.

Check Load Import Parameter (correct Codepage)  1100 single code page  4103 little endian  4102 big endian  SAP AG 2006. Roland Kramer / 25 25 . BW Systemcopy.

Roland Kramer / 26 26 . dbsnmp)  SAP AG 2006.Check Database user (outln. BW Systemcopy.

you will also have to restore the systems (BW and R/3) in the AWB. the SAP BW system and the source systems (R/3) and restore the connections in the AWB using RSA1. 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.  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. See the additional chapter “Restoring source systems.  SAP AG 2006.      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 27 . Check this with BD54. Check both. Check IDoc ports in WE21 for the systems. The BDLS transaction only converts the IDOCS. To complete the tasks. Roland Kramer / 27 Differences to the BW system copy:  Basically there are only two things to do after the system copy is fulfilled. BW Systemcopy. To restore the source systems.” Run the Program RS_BW_POST_MIGRATION Check the partner profiles in WE20 for the systems.Post Activities Following the SAP System Copy Creation        Run transaction BDLS for all systems. Check the IDoc type in WE30 for the systems. Note that the new logical source system names must not be in table TBDLS.

     SAP AG 2006. Check the protocol of the recreation in the SAP BW system.  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. Note that the new definition must not be in the table TBDLS (transaction BD54). Go to the SAP BW target system and use transaction RSA1  Source system and restore the desired SAP R/3 source system. Go to SM59 in the SAP BW target system. Roland Kramer / 28 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. BW Systemcopy. Go to WE20 in the SAP BW target system an delete the existing partner definition. create the new RFC connection and remove the old connection.

we recommend that you contact an SAP consultant before starting it. the data are not converted. sys. You must pay attention to this during the conversion itself.  All IDocs in the system must be processed beforehand since the logical system name could be contained in the IDoc data record. Manual post processing must be carried out in this case. The logical system name in IDoc data records would not be taken into account for conversion. and if necessary the conversion must be started again. on the other hand. Another reason is that certain data could be saved as part of fields in cluster or pool tables with regard to the logical system. If there are applications where the tables do not reference these domains. COFIO1). no other activities may be carried out in the system. Roland Kramer / 29 Further notes:  The conversion of the logical system name has far-reaching consequences.  SAP AG 2006.  During the run of the conversion report. 29 . the process must also be carried out in all partner systems.  The conversion report that was dynamically generated from Report RBDLSMAP (up to SAP Release 6. Therefore. The reason is that the relevant database tables are dynamically determined by certain domains (LOGSYS and EDI_PARNUM).10) can also be run in the background.  Export the list of conversion results (on the screen) to a local file for test purposes. this parameter should be as great as possible. In this case. it can cause errors for tables in which the logical system is key field or unique index (for example.  If the new logical system name already exists in the system. The following points should be observed:  In productive systems the conversion of the logical system name is not provided.  If a termination occurs due to the database roll area.Running the Conversion of Log. Therefore. In this case the number of converted entries is smaller than the number of selected entries. Names with BDLS Note that the new logical source system name must not be in table TBDLS. In order to gain performance.  After successfully completing the conversion.  The conversion is carried out in the current client. BW Systemcopy. you should either restart the roll area as high as possible or reduce the parameter 'Number of entries per commit' from the default value. user interaction is required in the online execution. all confirmation prompts are automatically confirmed with Yes during the run. if the corresponding input fields are filled with values. synchronize the table buffers in the server. Such data are not converted.

Action on the SAP R/3 Source System  SAP AG 2006. 30 . It is strictly recommended only to use the mentioned Function Modules to modify the Entries otherwise you can permanently destroy a working BW System. BW Systemcopy. Roland Kramer / 30   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.

31 . Roland Kramer / 31    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. See Note 128447 and 1167901 for Details. BW Systemcopy. An Alternative would also to use trusted System connection. Therefore you don‘t have to deal with Passwords again. due the Fact that when you copy SM59 connections the Password will not be copied.Deleting the Existing RFC Connection in BW with SM59  SAP AG 2006.

Deleting/Checking the Partner Profile in BW with WE20  SAP AG 2006. BW Systemcopy. Roland Kramer / 32 32 .

BW Systemcopy. Roland Kramer / 33  The restoring process take care of all Settings inside the ALE configuration.Checking IDoc Ports and Types with WE21 and WE30  SAP AG 2006. It is not necessary to use more transactions as    WE20 WE21 WE30 Partner Profiles IDOC Ports IDOC Types 33 .

BW Systemcopy. Roland Kramer / 34  The restore Process takes care of all ALE related Settings. 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 34 .Restoring the Source System in BW with RSA1  SAP AG 2006. No additional Customizing is necessary.

Maintaining Suggestions for the Extraction Users in BW  SAP AG 2006. If you are planning to replace the existing User with a new 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    35 . BW Systemcopy. Note that when you call one of these Transaction out of Transaction RSA1 (Administrator Workbench) you have also to close the RSA1 also. Roland Kramer / 35   When you are using different Users for the connection or users different from the Default you can change the Names at any time. because during the call of the Transaction some Table will be buffered. please make sure that you first restore the connection with the old user before you try to restore the Connection with another User.

No changes will be done afterwards. Changes in the customer name area Again. note that will have to open the systems during the connection. you can set up the changeability for the customer name area with Transaction SE03. You can set up the changeability with Transaction SE03 (Organizer Tools). Choose the entry Changes to Repository and Cross-Client Customizing Permitted in the field Changes to Cross-Client Objects.Prerequisites for the System Change Option  Note that for a successful source system connection. then Execute. Make the settings in the subsequent screen.  SAP AG 2006.     36 . In the source system. select the relevant client under Business Information Warehouse  Connections to Other Systems  General Connection Settings  Assign Logical System to Client. make this setting in the Implementation Guide under Cross-application Components  Distribution (ALE)  Basic Settings  Set Up Logical System  Assign Logical System to Client. Roland Kramer / 36  As a rule. you can set up the changeability of the BW namespace with Transaction SE03. Choose Organizer Tools  Administration  Set Up System Change Option. 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  Customer developments  Local developments (no automatic transport)  Business Warehouse SAP name space  Business Warehouse Customer name space HOME LOCAL /BI0/ /BIC/ modifiable modifiable modifiable modifiable modifiable  When you connect productive R/3 and ERP systems to the productive SAP BW system. then choose Goto  Detail. Afterwards you can close it again. mean changes as far as the system change option is concerned. Connecting a system as a source system to a BW or connecting a BW to a new source system will. however. BW Systemcopy. Cross-client Customizing and Repository changes In the BW Customizing Implementation Guide. Changes to BW namespaces /BIC/ and /BI0/ Again. Changes to the software components local developments and Business Information Warehouse. 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. no system changes are permitted in productive systems at all.

BW Systemcopy.Settings in SE06  SAP AG 2006. Roland Kramer / 37 37 .

BW Systemcopy. Roland Kramer / 38   To call the Application Log directly you can call this with Transaction SLG1 With Transaction SLG2 you can administrate the Application log.Checking the Protocol  SAP AG 2006. e.g. 38 . Delete old logs to save Disk space and get better Performance.

BW Systemcopy. Roland Kramer / 39 39 .Checking the Source System Afterwards  SAP AG 2006.

choose Tools  Administration  Management  Network  RFC Destinations in BW. Roland Kramer / 40 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_BIWX_RFC. BW  SBIW. For the user and password. BW  SCC4. BW  SU01 R/3.   40 . BW Systemcopy. enter the background user that you created in step 1. 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. The defined name. ALE communicates with the help of the SAP Business Information Warehouse name that you defined. Select Tools  Administration  Management  Network  RFC Destinations here in the source system. RSA1 R/3. BW  BD54 R/3. BW  SM59 Check the system settings before you connect them R/3. For user and password. what R/3. BW  SALE) R/3. Define the RFC destination parameters for the SAP source system in BW.Checklist for Connecting BW . therefore. Define the RFC destination parameters for the SAP Business Information Warehouse in the source system. SE06 Define the new source system (manually) (This is automatically starting a meta data upload) Customizing settings from the R/3 system (Do this before the first data load starts) Check/Transfer of global settings (Use this function as a simulation to check) Activate the necessary BC data sources Perform the meta data upload on the BW system BW  RSA1 R/3. represents an identification of the SAP Business Information Warehouse. 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. BW  SBIW. BW  SBIW R/3. BW  RSA1 R/3. To do this. RSA1  SAP AG 2006. Enter the information on the server name previously taken from the source system. 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.R/3 Checklist           Define user <SID>_ALEBW in BW and R/3 (Make sure you have the right permissions) Define logical system names (<SID>CLNT<client>) (Check ALE communication) Check RFC connection (with remote Logon) where.

BW Systemcopy. Roland Kramer / 41   Invalidate Generated Program reset timestamps to regenerate all generated programs Adapt DBDIFF to New DB Maintain exception table containing differences between Data Dictionary and DB Other Work only relevant for DB6 databases Adapt Aggregate Indexes Index Definition is checked and aligned for Aggregates Adapt Basis Cube Indexes Index Definition is checked and aligned for Cubes Generate New PSA Version this generates new PSA versions and only for this the source system connection must be available uses report rs_transtru_activate_all Delete Temporary Tables as mentioned Repair Fact View recreate Fact Views for InfoCubes (SAP_FACTVIEWS_RECREATE) Restriction to One Cube as mentioned Other Work as mentioned According to Note 771209 you should run the Report with the Variant POSTMGR.Run Program RS_BW_POST_MIGRATION after Import  SAP AG 2006. These contains the following Options:  Other Work  Delete Temporary Tables  Repair Fact View X X X         41 .

ODS object . 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 . see Notes 591382 and 424848 for more details. The Program synchronizes the delta Marker.SYSTEMCOPY. Roland Kramer / 42 Additions to the Transaction RSSGPCLA:  You may also run the Program RSSM_OLTP_INIT_DELTA_UPDATE for R/3 source systems.x for Note 849857    42 . This is needed if the BW System was copied with out copying the connected R/3 based System.Check and repair program BW7. For ODS Objects from BW system. if the BW System is a source of other BW Systems. This is needed also. BW Systemcopy. migration (RSSGPCLA)  SAP AG 2006. check with Note 518426 and use the Transaction RSSGPCLA.

SAP. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Produkte können länderspezifische Unterschiede aufweisen. ByDesign. and/or development. xApps. 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. einschließlich und ohne Einschränkung für direkte.  SAP AG 2006. 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. The statutory liability for personal injury and defective products is not affected. or other items contained within this material. developments. Die Informationen. die Eigentum anderer Softwarehersteller sind. SAP. ByDesign. SAP shall have no liability for damages of any kind including without limitation direct. Dies gilt u. zu welchem Zweck und in welcher Form auch immer. a. xApp. or consequential damages that may result from the use of these materials. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. R/3. weder ausdrücklich noch stillschweigend. SAP übernimmt keine Haftung für Schäden jeglicher Art. This document is provided without a warranty of any kind. eine Produktstrategie bzw. Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr. Duet. Texte. The information in this document is proprietary to SAP. xApp. einen bestimmten Geschäftsweg. This document contains only intended strategies. The information contained herein may be changed without prior notice. 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. SAP NetWeaver. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. graphics. either express or implied. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. This limitation shall not apply in cases of intent or gross negligence. auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen. text. including but not limited to the implied warranties of merchantability.. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. SAP does not warrant the accuracy or completeness of the information. Grafiken. National product specifications may vary. aber nicht ausschließlich. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. R/3. unterliegen nicht dem Einfluss von SAP. xApps. und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. BW Systemcopy. SAP assumes no responsibility for errors or omissions in this document. Alle Rechte vorbehalten. Roland Kramer / 43 43 . bereitgestellt. or non-infringement. special. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. -entwicklung einzuschlagen. SAP Business ByDesign. Duet. spezielle. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Copyright 2008 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. Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend. indirect. fitness for a particular purpose. product strategy. SAP Business ByDesign. links. Dieses Dokument enthält nur vorgesehene Strategien. SAP NetWeaver. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen. Data contained in this document serves informational purposes only. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. 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. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen.

Sign up to vote on this title
UsefulNot useful