Professional Documents
Culture Documents
BW source system ALE configuration: SAP source systems are identified via their logical
system name (assigned to each client in SCC4)
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.
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.
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.
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
Note 936441: Oracle 9.2 settings for R3load based system copy
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
142100
122814
117395
Note that for the BW 3.5 (Basis 6.40) the pilot project status is not needed anymore.
See Note 771209 for more Details
10
11
12
The temporary tablespace (tempsize) should be at least twice the size of the largest DB
index.
13
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
(2) Dictionary
temporary
(3) Locally
permanent
(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"
14
15
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, see
Note 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 #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.
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.
16
Splitting tables is only available on project basis for release 6.20 and above.
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
Note that you can always use the latest Version of the SPLIT tools (Basis 7.00)
17
Note
777024
620
SAP_BASIS 46
SAP_BASIS 58
771209
640
SAP_BASIS 10
SAP_BASIS 16
888210
700
SAP_BASIS 00
SAP_BASIS 07
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.
18
19
20
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 Endian
IBM 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 Endian
Alpha, Intel X86 (and clones), X86_64, Itanium (Windows + Linux), Solaris_X86_64
21
22
23
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
24
25
26
27
28
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 742009: ALE: BDLS for fields in the /xxx/ namespace dump
Note 110849: "Error during insert in port table" (create source system)
29
30
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.
31
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.
32
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 dont have to deal with
Passwords again. See Note 128447 and 1167901 for Details.
33
34
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
35
The restore Process takes care of all ALE related Settings. No additional Customizing is
necessary.
36
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
37
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.
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.
38
39
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.
40
41
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.
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.
42
Other Work
as mentioned
According to Note 771209 you should run the Report with the Variant POSTMGR.
These contains the following Options:
Other Work
43
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.
Note 1051664 - Check and repair program BW7.x for Note 849857
44
Additional Notes/Corrections
45
46