Académique Documents
Professionnel Documents
Culture Documents
Overview
Enterprise Data Warehousing and SAP BI Foundations and requirements Upgrade and the system landscape Alpha conversion Prepare and upgrade
SAP BW upgrade
Overview
Enterprise Data Warehousing and SAP BI Foundations and requirements Upgrade and the system landscape Alpha conversion Prepare and upgrade
SAP BW upgrade
SAP NetWeaver 04
SAP BW 3.5 (UrS) time
SAP AG 2005, 6
Jun Nov Mar Dec Dec 2002 2002 2004 2005 2006
Mar 2013
Components: Components: BI Content 3.3 BI Content 3.2 BW 3.1 Content SAP BW 3.0B SAP BW 2.1C SAP BW 2.0B
Content release
SAP AG 2005, 7
BW 2.1C BW 2.0B
Basis 4.6D Basis 4.6C
SAP AG 2005, 8
Web AS 6.40
Web AS 6.40
Minimum downtime 1~2 hours [downtime-minimized strategy] Upgrade runtime determined by CPU and I/O speed (not size)
* If already installed (SAP BW 3.1 or greater)
SAP AG 2005, 9
Executable versions (min): tp OS/390: 320.56.57 All other tps: 320.56.56 R3trans: 09.07.2002
Source: SAP note 658992
SAP AG 2005, 10
^ See SAP Note 318846 for Kernel (upgrade) installation info * See SAP Note 655941 for Plug-in upgrade info
Note: All recommended OS patches/patchsets should be applied. See specific OS/DB SAP notes for details.
Key tip: Source system plug-in can be the longest timeline in an upgrade project
Plan accordingly!
Plug-In/ Release SP level PI 2004.1 (SP lvls to be confirmed Check SAP notes) PI 2003.1 3.1I/SP SP/HR B2/C9 SP/HR B0/B4 4.0B/SP SP 38 4.5B/SP SP 19 4.6B/SP SP 3 4.6C/SP SP 1 4.7/SP SP 0 PI_Basis 2004_1_620 SP 0
SP 38
SP 16
SP 3
SP 1
Overview
Enterprise Data Warehousing and SAP BI Foundations and requirements Upgrade and the system landscape Alpha conversion Prepare and upgrade
SAP BW upgrade
Web
Server. ITS
SAP BW used ITS only as a gateway (WEBRFC) ITS Flow Logic was only used in special cases
WEB Browser
HTTP
mySAP Web AS
Enhanced scalability, performance, and robustness Generation of charts and maps on Internet Graphic Server (IGS) Support of background processing
IGS
SAP AG 2005, 13
All MIMEs and customer-owned CSS stored on the ITS should be transferred to the MIMEs Repository For IGS known bugs and solutions, see OSS Note 459674
SAP AG 2005, 14
HTTP
BW 3.x Web AS
RFC/HTTP RFC
HTML +Java
Internet
ChartEngine
IGS
GIS Engine
EP 5.0
SAP Dialog-Protocol and AutomationCalls HTTP Protocol, for HTML, JavaScript, Java Applets, etc.
External system
The user never calls IGS directly; graphics generation is server : server
SAP AG 2005, 15
ICM
ICM
ICM
WP
WP
WP
WP
WP
WP
WP
WP
SAP BW System
RFC Dest
System boundaries* Network Communication component Data conversion (syntax) Data interpreter (semantics) Component Workload-balancing check
PW PW Portwatcher Portwatcher SAP BW SAP BW Chart Interpreter Chart Interpreter Chart Chart Control Control
PW PW Portwatcher Portwatcher SAP BW SAP BW Interpreter Chart Interpreter Chart for GIS Interpreter for GIS Interpreter Chart Chart Control Control Geocoder Geocoder
PW PW Portwatcher Portwatcher
SAP AG 2005, 16
WP
CI
MS MS
disp disp
disp disp
ICM
ICM
WP
WP
WP
WP
WP
RFC Dest
RFC Dest
RFC HTTP HTTP RFC Listener Listener Listener Listener MUX MUX Multiplexer Multiplexer
RFC HTTP HTTP RFC Listener Listener Listener Listener MUX MUX Multiplexer Multiplexer
PW PW Portwatcher Portwatcher SAP BW SAP BW Chart Interpreter Chart Interpreter Chart Chart Control Control
PW PW Portwatcher Portwatcher SAP BW Interpreter SAP BW Interpreter Chart Chart for GIS Interpreter Interpreter for GIS Chart Chart Geocoder Geocoder Control Control
PW PW Portwatcher Portwatcher SAP BW SAP BW Chart Interpreter Chart Interpreter Chart Chart Control Control
WP
PW PW Portwatcher Portwatcher Zip Interpreter Zip Interpreter Zipper Zipper
PW PW Portwatcher Portwatcher SAP BW Interpreter SAP BW Interpreter Chart Chart for GIS Interpreter Interpreter for GIS Chart Chart Geocoder Geocoder Control Control
SAP AG 2005, 17
SAP BW 3.5)
If your source release is SAP BW 2.x, you must have completed the conversion of the Web objects successfully see Upgrade Guide
The conversion of the chart settings is based on the prior successful conversion of the Web Objects If you start the conversion of the chart settings although the Web objects conversion did not succeed, you can no longer repeat the Web Objects conversion. Then, you must correct all open problems manually!
SAP AG 2005, 18
Overview
Enterprise Data Warehousing and SAP BI Foundations and requirements Upgrade and the system landscape Alpha conversion Prepare and upgrade
SAP BW upgrade
Note: These decisions should be made with your SAP BW Administrators! All characteristics found are listed in three groups
Characteristics with collisions in the SID table
Marked in red Neither remove nor convert is suggested the user must decide which
Compounded characteristics must be converted in one step Note: The system lock remains active during the maintenance
SAP AG 2005, 20
The data extraction and loading must be consistent; previously, a warning was given only if transfer rules in SAP BW and R/3 extraction were different (some content InfoObjects were initially delivered incorrectly)
Trans. Structure Char 4 0 0 0 1 0 1
SAP AG 2005, 21
Comm. Structure Char 6 0 0 0 1 0 1 Values are not found when entered on Dynpro
Check job status Start the check job Conversion decisions Conversion job status
Overview
Enterprise Data Warehousing and SAP BI Foundations and Requirements Upgrade and the system landscape Alpha conversion Prepare and upgrade
SAP BW upgrade
Initialization
Extension Integration
CHECK modules
SAP AG 2005, 24
6.40
6.40
SAP BW DATA 4.6x* 6.40
Shado
w ins tallati
on
Import
* Example: 2.x -> 3.5 upgrade (4.6x) 3.x -> 3.5 would use 6.20
SAP AG 2005, 25
DA TA
conv
ersio
XPRA SAP BW
Phase
DATA
6.40
Patches of central Basis dictionary objects Ability to distribute upgrade processing to different servers
Costs:
Increased overall runtime
Start-to-finish time is increased
f f o
on
SAP AG 2005, 26
Support Packs
Modification Adjustment
Activation Distribution
Add-Ons
Inst.
Uptime
Backup PREPARE Upgrade
Upgrade
Backup
ICNV
Downtime-Minimized Downtime-Minimized
New Rel.
Imp.
Backup
Downtime
Backup
Resource-Minimized
Post Upgrade
SAP AG 2005, 28
Do not ignore any phase unless directed by SAP BW development Do not jump phases Tip: Start R3up at end of the day; continue next morning
With luck, the upgrade will be far along the next morning Upgrade guide will help you determine which phases require user input. 6.40 PREPARE eliminates most of the user input for R3up.
SAP AG 2005, 29
SAP AG 2005, 30
Overview
Enterprise Data Warehousing and SAP BI Unicode concepts SAP BW and Unicode SAP BW Unicode migration
Overview
Enterprise Data Warehousing and SAP BI Unicode concepts SAP BW and Unicode SAP BW Unicode migration
Unicode Essentials
What is Unicode?
Character encoding schema for (nearly) all characters used worldwide includes nearly 100,000 distinct language characters!
Afar Abkhazia Avestan Afrikaans Amharic Arabic Assamese Aymara Azerbaijani Bashkir Belarusia Bulgarian
Dzongkha Greek Bihari English Bislama Esperanto Bengali Spanish Tibetan Estonian Breton Basque Bosnian Persian Catalan Finnish Chechen Fijian Chamorro Faroese Corsican French Czech Frisian Church Slavic Irish Chuvash Gaelic Welsh Gallegan Danish Guarani German Gujarati
Manx Hausa Hebrew Hindi Hiri Motu Croatian Hungarian Armenian Herero Interlingua Indonesian Interlingue Inupiak Icelandic Italian Inuktitut Japanese Javanese Georgian Kikuyu
Marathi Malay Maltese Burmese Nauru Norwegian Bokml Ndebele Nepali Ndonga Dutch Norweg. Nynorsk Norwegian Ndebele Navajo Nyanja Occitan Oromo Oriya Ossetian Panjabi
Pali Polish Pushto Portuguese Quechua Raeto-Romance Rundi Romanian Russian Kinyarwanda Sanskrit Sardinian Sindhi Northern Sami Sango Serbo-Croatian Sinhalese Slovak
Telugu Tajik Thai Tigrinya Turkmen Tagalog Tswana Tonga Turkish Tsonga Tatar Twi Tahitian Uighur Ukrainian Urdu
Uzbek Vietnamese Volapk Wolof Xhosa Yiddish Yoruba Reserved- cust. Zhuang Chinese trad. Chinese Zulu
SAP AG 2005, 35
English
Thai Croatian Czech Hungarian Polish Romanian Slovak Slovenian
Danish Dutch German Finnish French, Italian Norwegian Portuguese Spanish Swedish Turkish
SAP AG 2005, 36
Overview
Enterprise Data Warehousing and SAP BI Unicode concepts SAP BW and Unicode SAP BW Unicode migration
As with all other SAP NetWeaver 04 components, SAP BW 3.5 supports Unicode
For SAP BW, Unicode is optional
Customers can continue using non-Unicode SAP BW or choose to migrate to Unicode Even though Web AS 6.40 J2EE requires Unicode, it is possible to continue using non-Unicode SAP BW
SAP BW supports extraction from Unicode, non-Unicode, and MDMP source systems
SAP AG 2005, 38
Unicode-Compliant SAP BW
SAP BW can extract data from Source Systems with specific code pages (non-Unicode or Unicode)
SAP BW can extract data from SAP Source System running mixed code pages (MDMP) Interfaces to third-party systems support correct code page conversion
SAP AG 2005, 39
Which versions of SAP BW are released for Unicode and when are they available?
SAP BW Unicode releases
SAP BW 3.5 as part of SAP NetWeaver 04 and all subsequent releases [SAP BW 3.1 Content has been piloted, but it is not shipped anymore]
Availability dates Unicode has been generally available with SAP BW 3.5 (NetWeaver 04) since Sept 1st 2004 Unicode Conversion: Only available for SAP BW 3.5 (new SAP BW migration tool delivered)
SAP AG 2005, 40
Overview
Enterprise Data Warehousing and SAP BI Unicode concepts SAP BW and Unicode SAP BW Unicode migration
The Unicode Conversion Project: Overview Preparation Conversion Post -Conversion Post-Conversion
Set up the Unicode upgrade project Perform list of tasks to prepare system for migration
To be done during system downtime Export/import process entire database contents Use of SAP BW migration tool Up and Running Verification of Data Consistency Integration Testing focused on language handling
SAP AG 2005, 44
SUMG
Post-Conversion Repairs Database Conversion in Unicode Export, Preparation system Conversion in non-Unicode & Import system
SAP AG 2005, 45
SUMG
Post-Conversion Repairs Database Conversion in Unicode Export, Preparation system Conversion, in non-Unicode and Import system
SAP AG 2005, 46
Also the standard R/3 platform and database-dependent installation guide have to be used, which can be found in: Standard Installation Guide Directory: SAPNet Installation Guide Directory
SAP AG 2005, 47
SAP AG 2005, 48
R3Load Export
SAPInst is used as Frontend tool
Logs are written to the SAPInst directory Export Files are written to the Export directory
Conversion (non-UC
Non-UC R3Load
SAP AG 2005, 49
R3Load Import
SAPInst is used as frontend tool
Non-UC database can be deleted or UC database can be installed on different server Import procedure nearly same as new installation Special SAP BW objects procedures included
UC R3Load R3load.exe -i ....
Export DIR: SAPAPPL0.001 SAPAPPL1.001 ... . . Multiple processes possible. Number of processes same as during export (default)
SAP AG 2005, 50
SUMG
PostConversion Repairs in Conversion Database Unicode Preparation Export, Conversion system in non-Unicode & Import system
SAP AG 2005, 51
SAP AG 2005, 52
Average speed for exporting 880 GB: 3.36 GB/hour/CPU Total size of the export dump files: 194 GB
SAP AG 2005, 53
Average speed for importing 880 GB: 14.4 GB/hour/CPU Average speed for importing 194 GB dump size: 3.17 GB/hour/CPU
SAP AG 2005, 54
SAP AG 2005, 55
Overview
Enterprise Data Warehousing and SAP BI System landscape configuration System copy: SAP BW and Source System together System copy: SAP BW refresh w/o Source System System copy: Source System refresh w/o SAP BW
Overview
Enterprise Data Warehousing and SAP BI System landscape configuration System copy: SAP BW and Source System together System copy: SAP BW refresh w/o Source System System copy: Source System refresh w/o SAP BW
It should be noted that as Data Warehouses and OLTP systems grow, the resource impact of system refreshes also grows
SAP AG 2005, 59
R/3 system
Client 100 LogSys: BWCL100 Client 200 LogSys: R3CL200 Client 300 LogSys: R3CL300 Client 100 LogSys: BWCL100
SAP BW system
SAP AG 2005, 60
R/3 system
SAP BW system
R/3 system
CRM
CRD
ALE/RFC
Transports
Transports
CRQ
ALE/RFC
CRP
ALE/RFC
BW
Transports Transports
BWD
ALE/RFC
BWQ
ALE/RFC
BWP
ALE/RFC
R/3
R3D
Transports
Transports
R3Q
R3P
* Note: The same principle applies to any SAP Source System (SAP APO, mySAP CRM, SAP BW, etc.)
SAP AG 2005, 61
SAP BW
BWD
ALE/RFC
Transports
Transports
BWQ
ALE/RFC
BWP
ALE/RFC
R/3
Example: SAP BW client and one R/3 client as a Source System
SAP AG 2005, 62
Transports
Transports
Note: There are restrictions with such an approach, particularly in complex ALE scenarios and system connections that span system types 2. Using unique logical system names across systems in the same landscape, and unique logical system names within each system type (DEV, QAS, PRD) DEV
Logical System: BWDCL100
QAS
Logical System: BWQCL100
PRD
Logical System: BWPCL100
SAP BW
BWD
ALE/RFC
Transports
Transports
BWQ
ALE/RFC
BWP
ALE/RFC
R/3
Example: SAP BW client and one R/3 client as a Source System
SAP AG 2005, 63
Transports
Transports
Option 2
Overview
Enterprise Data Warehousing and SAP BI System landscape configuration System copy: SAP BW and Source System together System copy: SAP BW refresh w/o Source System System copy: Source System refresh w/o SAP BW
Depending on your choice of LSN strategy, there are two options available:
1) Using non-unique LSNs across systems in the same landscape (see diagram below):
1. 2. 3.
On BWT, change the Source System RFC Destination host names to the new host for R3T On BWT, check the RFC destination host name for the BWT Source System (blank) On R3T, change the Source System RFC Destination host names to the new host for BWT DEV
Logical System: BWCL100
QAS
Logical System: BWCL100
PRD
Logical System: BWCL100
TST
Logical System: BWCL100
SAP BW
Example: Create an upgrade Testing system BWD
ALE/RFC
Transports
Transports
BWQ
ALE/RFC
BWP
ALE/RFC
Copy
BWT
ALE/RFC
R/3
R3D Logical System: R3CL200
SAP AG 2005, 67
Transports
Transports
2.
3.
QAS
Logical System: BWQCL100
PRD
Logical System: BWPCL100
TST
Logical System: BWTCL100
SAP BW
Example: Create an upgrade Testing system
Transports ALE/RFC Transports ALE/RFC
BWD
BWQ
ALE/RFC
BWP
Copy
ALE/RFC
BWT
R/3
R3D Logical System: R3DCL200
SAP AG 2005, 68
Transports
Transports
BWTCL100
5.
On R3T, create a new RFC destination for the BWT SAP BW system
Copy existing entry BWPCL100, creating new RFC destination BWTCL100 Delete the old RFC destination BWPCL100
6.
* Warning:
Converting the logical system for an R/3 system can be very time consuming. The runtime is dependent on whether ALE has been enabled on your R/3 system for certain documents. If so, a large number of documents (sales orders, etc.) may be tagged with the logical system name for ALE purposes. These would have to be converted. It is suggested that you analyze your R/3 system before executing this conversion (BDLS has a test function, but runtimes can be just as long as the conversion itself) Note: Connecting SAP BW to your R/3 system does not enable this ALE functionality!
SAP AG 2005, 69
The SAP BW steps to perform after this refresh are the same as previously outlined in the system copy procedure
Optional: You can add steps to save SAP BW Objects from the old SAP BW System and Source systems
DEV
Logical System: BWCL100
QAS
Logical System: BWCL100
Copy
PRD
Logical System: BWCL100
SAP BW
BWD
ALE/RFC
Transports
Transports
BWQ
ALE/RFC
BWP
ALE/RFC
R/3
R3D Logical System: R3CL200
Transports
Transports
Copy
SAP AG 2005, 70
Cons:
Coordination of timing for the system refresh All work in QAS systems must be completed and imported into PRD or reapplied after refresh
SAP AG 2005, 71
Overview
Enterprise Data Warehousing and SAP BI System landscape configuration System copy: SAP BW and Source System together System copy: SAP BW refresh w/o Source System System copy: Source System refresh w/o SAP BW
BW
BWD
ALE/RFC
Transports
Transports
BWQ
ALE/RFC
BWP
ALE/RFC
R/3
Example: SAP BW client and one R/3 client as a Source System Unique LSNs
SAP AG 2005, 73
Transports
Transports
1. Prior to the refresh, in the SAP BW System to be refreshed, delete the R/3 Source Systems
Note: In our example, this would occur in BWQ before the refresh from BWP
2. Perform the system refresh. If logical system name is to be changed, execute a logical system renaming process (transaction BDLS) 3. In the newly refreshed SAP BW system, create a new RFC destination for the BWQ Source System and delete the old BWP RFC destination 4. In the newly refreshed SAP BW system, delete the original Source System connection. (connection to R3PCL200 in our example)
1. 2.
Warning: Ensure that the RFC Destination is not functioning (dummy)! In the Admin Workbench, delete the R/3 Source System (R3PCL200). This may take some time as all the transfer rules and PSA tables are deleted
SAP AG 2005, 74
7. Optional: In the newly refreshed SAP BW system, recreate the SourceSystem-dependent SAP BW objects using the Save for System copy Transport. This saves you considerable manual work
1. In the Transport Connection, select the Conv. of log. Sys name button 2. Create a mapping for the SAP BW system to itself (Mapping of BWQCL100 to BWQCL100) 3. Import the Save for System copy transport into the SAP BW system
SAP AG 2005, 75
Overview
Enterprise Data Warehousing and SAP BI System landscape configuration System copy: SAP BW and Source System together System copy: SAP BW refresh w/o Source System System copy: Source System refresh w/o SAP BW
QAS
Logical System: BWQCL100
PRD
Logical System: BWPCL100
SAP BW
BWD
ALE/RFC
Transports
Transports
BWQ
ALE/RFC
BWP
ALE/RFC
R/3
Example: SAP BW client and one R/3 client as a Source System Unique LSNs
SAP AG 2005, 77
Transports
Transports
Copy
1. Perform the normal technical system refresh procedures 2. In the newly refreshed Source System, delete the original Source System connection (The connection to R3PCL200 in our example)
1.
Disable the RFC Connection for BWPCL100 This disables the interface from the Source System to SAP BW, and ensures we do not connect to the production SAP BW system Delete the DataSource and connection information for the old SAP BW system that was overwritten If logical system name is to be changed, execute a logical system renaming process (transaction BDLS) Execute BDLS to convert R/3 client LSN from R3PCL200 to R3QCL200
2.
3.
4.
SAP AG 2005, 78
SAP AG 2005, 79
SAP AG 2005, 81
SAP NetWeaver
http://service.sap.com/NetWeaver
Unicode
http://service.sap.com/globalization
Release Notes
http://service.sap.com/releasenotes
SAP Plug-In
http://service.sap.com/R3-Plug-In
SAP SDN
http://sdn.sap.com
Safeguarding
http://service.sap.com/safeguarding
Maintenance Strategy
http://service.sap.com/maintenancestrategy
Safeguarding Upgrade
http://service.sap.com/safeguardingupgr ade
SAP AG 2005, 82
Questions?
SAP AG 2005, 84
Feedback
Please complete your session evaluation and drop it in the box on your way out.
ronald.silberstein@sap.com
SAP AG 2005, 85
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. 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. Please note that this document is subject to change and may be changed by SAP at any time without notice. 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
SAP AG 2005, 86