WDEBU7 BI and ECC in One System

WDEBU7 Workshop Chapter 08 NW 2004(s) BI and ECC Deployment Options
Roland Kramer Rampup Coach nw2004s SAP Switzerland
NW 2004(s) BI and ECC (Core) Deployment Options
Introduction mySAP ERP Deployment Options Installation Scenarios Technical Remarks
The challenge of Sizing and Designing

Client-Server Client-Server ESA ESA TCO + ROI TCO + ROI
Applications Applications Platforms Platforms DBMSs DBMSs Operating Systems Operating Systems
SAP Enterprise Core Components (ECC)

Financials SCM HCM Development Development Testing Testing Production Production
SAP Clients SAP Clients DBs, DB Schemas DBs, DB Schemas
OLTP OLTP OLAP OLAP Servers Servers Networks Networks
SAP NetWeaver 2004(s) SAP NetWeaver Business Intelligence

SAP NetWeaver Application Server SAP DDIC SAP DDIC . DB Repository DB Repository
Operating System
Database Management System
Multiple Components One DB Multiple Components One DB Multiple Components One Multiple Components One System System
MCOD MCOD MCOS MCOS
DBSL, ODBC, JDBC DBSL, ODBC, JDBC
SAP AG 2003, Title of Presentation, Speaker Name / 4
Growing Complexity vs. TCO Reduction

mySAP Business Suite SCM PLM ERP SRM CRM Analytics SAP R/3 NetWeaver
R/3
R/3
Hardware Costs Implementation Costs Operation Costs
TCO Drivers
Hardware
Too many servers No joint resource utilization Oversized system landscape
Implementation
Different implementation guidelines Multiple independent and overlapping customization systems Complex Customizing (x100,000 customizing parameters) No end-to-end process verification Massive testing effort
Operations
No unified system management Complex multicomponent dependencies Error prone crosscomponent system integration Costly cross-system change management
Our Costs of Development
The true costs are the full lifecycle costs

Maintenance costs by far exceed initial development costs The value/effort ratio for development decreases over lifetime Costs multiply with the combination of multiple releases and multiple components that have to be maintained
Complexity is the main cost driver

Complexity drives cost growth exponentially The number of one-toone integrated system components increases complexity Complexity management is an architectural problem
Poor quality erodes profitability

Poor quality leads to a cost explosion in all lines of business Quality problems in a mass product are the hardest to fix Only quality per design leads to scalable business
mySAP ERP Running on Top of SAP NetWeaver

Front End
Front End
SAP GUI
w/ BI Ext
Web Browser
SAP ECC
System 1: SAP NW 04 and SAP ECC in One System

(BI and ECC in different clients)
Separate System 2: SAP NetWeaver 04 running XI Clients
ECC
BP ESS/MSS
SAP NetWeaver 04 running BI, EP
BI Content BI Functionality XI Functionality XI Functionality XI Functionality MI Functionality MI Functionality MI Functionality KW Functionality KW Functionality KW Functionality Web AS ABAP
KMC Portal Platform
BI Analy Prec Serv TREX BI Functionality BI Functionality BI Functionality XI Functionality XI MI Functionality MI Functionality MI Functionality J2SE Adapter Adapter Engine
BI Java Components
Adobe DS
KW Functionality KW Functionality KW Functionality Web AS ABAP Web AS Java
Web AS Java
ABAP Stack
Java Stack
Database
Additional Components
ABAP Stack
Java Stack
Database
Additional Components
ABAP
Java
ABAP
Java
SAP ECC 5.0 mySAP ERP 2004
SAP ECC 5.00 is the central component of mySAP ERP 2004

(ECC = ERP Central Component)
SAP ECC 5.0

Extension Sets EE EE EE
Add-On Add-On Add-On
Making full use of SAP NetWeaver

A
Add-Ons are still delivered separately. These Add-On modifications require additional effort to apply Support Packages The BI Business Content (BC) is installed as Add-on on top on NW04.
SAP ECC Core Add-On SAP NetWeaver `04 BI-BC
10
SAP ECC 6.0 mySAP ERP 2005

Industry solutions shipped in my SAP ERP 2005 are technically realized:
C within the cross-industry
applications Core
IE as Industry & Enterprise
SAP ECC 6.0

Enterprise & Industry Extensions
Former Add-On Former Add-On Former Add-On Former Add-On BI-BC
Extensions of mySAP ERP to be activated via the SAP Switch Framework -> applies to most Industry Solutions that were formerly provided via Add-Ons or Extension Sets (no modifications to the core anymore!!)
A as Add-Ons -> Only these few
EE
EE
EE
IE
IE
IE
SAP ECC Core SAP NetWeaver 2004s
remaining industry-specific applications are shipped separately and carry their own release or as a combination of the above-mentioned possibilities
11
12
Deployment Options with mySAP ERP

Target: Customer wants to benefit from the business intelligence capabilities provided by mySAP ERP
Today: Customer operates SAP R/3 4.6C only Today: Option A: Option B: Option C*:
SAP R/3 4.6C
SAP R/3 4.6C

Stay
NW04 BI
Install and implement
SAP R/3
Enterprise Upgrade
NW04 BI
SAP ECC NW04 BI

Upgrade and implement
+ No effort required for SAP R/3 upgrade + Immediate start of BI implementation - SAP R/3 upgrade still required by 2006
+ Add. functionality and benefits provided by SAP R/3 Enterprise + Longer mainstream maintenance for SAP R/3 Enterprise - Higher effort (upgrade and implementation in same time frame)
+ Add. functionality and benefits provided by SAP ECC + Lower TCO through integrated BI - Resizing of server landscape required
* These are examples only. More options might be available to the individual customer
To give you some ideas of possible deployment options with mySAP ERP, the following slides will show some of the most common examples. Each slide describes a specific customer situation (today) and the desired target. Please note that this presentation will not cover all the possible options! Target: A customer undertook a contract conversion to mySAP ERP and now wants to benefit from the Business Information Warehouse capabilities provided with mySAP ERP. Situation today: The customer operates SAP R/3 Release 4.6C. No other components are implemented at this point Possible Option A: The customer keeps SAP R/3 on release 4.6C and immediately starts the implementation of an new installed SAP BI system. The advantage of this option is that the customer can benefit from SAP BI as soon as possible without spending time on an upgrade at SAP R/3 level. However, since SAP R/3 4.6C is only under mainstream maintenance until 2006, it is clear that the customer will need to upgrade to SAP R/3 Enterprise or SAP ECC afterwards. Possible Option B: Customer performs upgrade to SAP R/3 Enterprise. In parallel or afterwards (depending on the available resources), it starts installation and implementation of SAP BI. The benefit of this option is that the customer is on a SAP R/3 release which offers long-term mainstream maintenance until 2009, while making the SAP BI capabilities available as soon as possible. From an effort perspective, this option requires more resources in a shorter timeframe than option 1. Possible Option C: Customer waits until SAP ECC becomes available (planned January 2005) and performs an upgrade to it then. After the upgrade, it starts implementation of integrated SAP BI. The disadvantage of this option is definitely the availability of SAP ECC. However, the advantage is that the customer can benefit from the integrated SAP BI, which offers the lowest TCO in these three options.
13
Deployment Options with mySAP ERP (cont.)

Target: Customer wants to benefit from the business intelligence capabilities provided by mySAP ERP
Today: Customer operates SAP R/3 4.0B and SAP BW 3.0B/3.1 Today: Option A: Option B: Option C*:
SAP R/3 4.0B
SAP BW 3.0B/3.1
SAP R/3
Enterprise Upgrade
SAP BW 3.0B/3.1
Stay
SAP ECC
Upgrade
NW04 BI
Upgrade
SAP ECC NW04 BI

Upgrade and migrate SAP BI
+ Add. functionality provided by SAP R/3 Enterprise
+ Add. functionality provided by SAP ECC + Long maintenance for SAP ECC and SAP BI
+ Add. functionality provided by SAP ECC + Lower TCO through integrated SAP BI - Resizing of server landscape required
- End of maintenance for SAP BI 3.0B is December 31, 2006 - Functionality in SAP BW is still limited to SAP BW 3.0B
- Higher effort (both upgrades in same timeframe)
Target: A customer undertook a contract conversion to mySAP ERP and now wants to benefit from the Business Information Warehouse capabilities provided with mySAP ERP. Situation today: Compared with the previous customer example, this customer operates SAP R/3 Release 4.0B where mainstream maintenance ended on December 31, 2003. Furthermore, this customer runs a SAP BI system on release 3.0B. Possible Option A: The customer performs an upgrade to SAP R/3 Enterprise, which is already available, and stays on the SAP BI system. With this the customer can benefit immediately from the new features brought by SAP R/3 Enterprise, utilizing the SAP BI capabilities. Possible Option B: The customer waits* until SAP ECC becomes available (planned January 2005) and performs upgrade to SAP ECC. In parallel or afterwards (depending on the available resources), the customer starts upgrade of SAP BI to the latest release. In contrast to option A, this would offer latest processes and functions available with mySAP ERP. Possible Option C: Customer waits until SAP ECC becomes available and performs an upgrade to it then. After the upgrade, it starts implementation of integrated SAP BI. The advantage compared with option B is that the customer can benefit from the integrated SAP BI, which offers him the lowest TCO in these three options. Please contact SAP Consulting for SAP BI migration.
* Maintenance Extension required if customer doesnt want to enter customer specific maintenance.
14
Deployment Options with mySAP ERP (cont.)

Target: Customer wants to benefit from the Self-Services and the Business Information Warehouse capabilities provided by mySAP ERP
Today: Customer operates SAP R/3 3.1I and SAP ITS Today: Option A: Option B: Option C*:
SAP ITS SAP R/3 3.1I SAP ITS SAP R/3

Enterprise Upgrade Stay/upgrade
SAP ECC SAP ITS

Upgrade and migrate ITS
NW04 BI
SAP ECC NW04 BI Upgrade, SAP ITS implement

BI and migrate ITS
NW04 BI
+ Add. functionality provided by SAP R/3 Enterprise + Long maintenance (SAP BI and SAP R/3 Enterprise) - Upgrade to SAP ITS might be required - Higher TCO
+ Add. functionality provided by SAP ECC + Longer maintenance + Utilization of integrated ITS - Customer needs to wait until SAP ECC becomes available - SAP BI still requires own system
+ Add. functionality provided by SAP ECC + Longer maintenance + Utilization of integrated SAP BI and SAP ITS - Resizing of server landscape required
Target: A customer undertook a contract conversion to mySAP ERP and now wants to benefit from the Self Services and the Business Information Warehouse capabilities provided with mySAP ERP. Situation today: The customer runs SAP R/3 Release 3.1I, in which case mainstream maintenance ended on December 31, 2003. Furthermore, this customer runs a SAP Internet Transaction Server 6.20 Possible Option A: One possible option is that the customer starts at least an upgrade to SAP R/3 Enterprise. Furthermore, he can keep the SAP ITS (or he upgrades it to the latest release) and implements SAP BI 3.5. Possible Option B: Another options this customer has, is to wait until SAP ECC becomes available to start an upgrade project to this component. After this step, the customer can utilize the integrated SAP ITS. Furthermore, this option shows, that a customer has still the option to implement and run a SAP BI beside SAP ECC. Possible Option C: Finally, another could example is that the customer does an upgrade to SAP ECC (if available) and utilizes the integrated SAP BI and SAP ITS. For sure, out of these options, the third option offers the lowest TCO and shows directly the benefit of SAP ECC from a TCO perspective.
15
16
Installation Scenarios: Shared nothing concept
Box 1 Operating System WAS Application
Box 2 Operating System WAS Application Todays Todays most often most often Installed Installed Scenario Scenario
SAP ECC
Clients 008, 009,
SAP BI
Client 011
ABAP/JAVA OLTP
DBSL/JDBC
ABAP/JAVA
DBSL/JDBC
OLAP
Oracle DB Schemas ABAP/J2EE
Oracle DB
Load
Schemas ABAP/J2EE
SAP ECC
SAP BI
17
Shared nothing concept

Pros robust, approved, scalable two DB-Instances with two schemas each Two Application Servers with one SAP Application each OLTP- and OLAP- processes properly decoupled in this case ECC could be installed upon the second Application Server in order to improve availability, performance and stability for a certain component coming from OLTP based Information Systems like LIS this was a big step forward in the end of the 1990ies Does SAP NetWeaver 04 Does SAP NetWeaver 04 give good reasons to give good reasons to change running change running installations? installations? Cons Too many boxes? Risk of Network traffic? Administration efforts?
normally not really
18
Scenarios, Principles, Procedures

SAP SAP Terminology Terminology
MDMP Multiple Display Multiple Processing

Several Codepages are used with the same Database
Note 745030 MDMP - Unicode Interfaces: Solution Overview MCOD Multiple Components One Database
Several components share the same Database
Note 712777 MCOD operation of R3 and BI in a database MCOS Multiple Components One System
Several components share the same Database Schema
Note 855534 Embedded NetWeaver Components in ERP
19
Scenario MCOD: Multi Components One Database

Box Operating System NW AP 1 Application NW AP 2 Application
SAP ECC
Clients 008, 009,
SAP BI
Client 011
ABAP/JAVA OLTP
DBSL/JDBC
ABAP/JAVA
DBSL/JDBC
Two WAS on One box OLAP
Oracle DB Schemas ABAP/J2EE Schemas ABAP/J2EE
SAP ECC
SAP BI
getting one getting one DB instance with DB instance with several schemas several schemas using logon Trigger* using logon Trigger*
* Session oriented settings for OLAP based systems like BI

20
MCOD: Multi Components One Database

Pros everything on one box, ABAP and J2EE no network migration tool for schema merging available ERP and BI are using different ABAP stacks migration tools available for copying a DB schema into another DB lower DB license costs Cons several schemas in one DBMS two NW Application Platforms on one server is possible, and necessary here because of different OLTP/OLAP settings Servers have to be resized only DB Administration costs reduced
Might be an option if you Might be an option if you start from the scratch, start from the scratch, but how do you handle the but how do you handle the reorganization of your reorganization of your system landscape in case system landscape in case of growth ? of growth ?
21
Scenario MCOS Multiple Components One System

Box Operating System NW AP Application One WAS with several Clients
SAP ECC/BI
Clients 008, 009, , 011
ABAP/JAVA OLTP/ OLAP

DBSL/JDBC
Oracle DB Schemas ABAP/J2EE
SAP ECC/BI
one DB Schema. one DB Schema. Logon Trigger* are Logon Trigger* are not possible not possible
* Session oriented settings for OLAP based systems like BI

22
Scenario MCOS/MCOD: SAP HR with BI and ESS 2005

ERP 2005 Operating System CI ABAP ECC/BI 000, 001, 002, 066 000 JAVA
JDBC 03 01 02
Selected Java Applications: EP SLD SLM NWA BI-Java ESS 2005
CI JAVA J2EE 7.00
ABAP
DBSL
SCS Manager DI JAVA Schema JAVA
DI ABAP Schema ABAP
SAP<SID>
SAP<SID>DB
23
MCOS Multiple Components One System

Pros minimized number of servers No network bottle neck reduced Administration costs optimized DB usage ECC components can easily deal with BI data Cons Additive Sizing will lead to an increased number of CPUs for this single box Prices for servers are increasing supra linear (faster) with the number of CPUs Can be implemented with acknowledge of SAP RIG Review In case of growth the scalability is reduced by the maximum number of CPUs of your system
Might be an option if you Might be an option if you start with BI in aasmall start with BI in small scenario. You will switch scenario. You will switch ASAP to separate Boxes. ASAP to separate Boxes.
24
25
An MDMP Configuration is not supported with BI
So, if your R/3 System is upgraded from 4.7 Enterprise (Basis 6.20) to ECC 5.0 (mySAP ERP 2004) and it was used with several Codepages (MDMP) you must first convert the System to Unicode before you can use the BI (Netweaver 04) functionality in a MCOS configuration. See also Note 747036.
26
Select the BI support stack queue (if wanted)
BI has some dependences to the ABAP and Basis Support Stack, due the fact that is part of the Netweaver 04/04s Stack.
27
Note the dependences between ECC and BI
28
Install the latest Business Content (BC) if wanted
Additional Notes: Note 653814: BI Content add-on dependencies for NetWeaver/SAP_BW Note 774933: Installation and upgrade to BI_CONT 3.53 Note 943365: BI_CONT 3.53: Information on Add-On Support Packages Note 847019: BI_CONT 7.02: Installation and Upgrade Information Note 920323: Installation BI_CONT 702 terminates during XPRA phase Note 929197: Release Restrictions for SAP NW2004s, BI Content Add-On 3 Note 916834: BI_CONT 7.03: Installation and Upgrade Information
29
Which Type of Support Package to use with NW04 BI

WP-PI 6.00 is Integrated in the Basis PI (PIB) Up to 6.40 Base System every R/3 based system needs the R/3 PI
This is also valid for ERP2004
R/3 PI 2004.1
Dependencies of Support Packages
SAP SPAM/SAINT 6.40 ECC 5.0

BI 3.5 is part of the Netweaver 04 Stack The SAP PIB is integrated with the Netweaver Stack New with Basis 6.40 is the integration of the other PIs like WP-PI in the Basis PI
BI BC 3.5.x
SEM 4.0
FIN 3.0
XI 3.0
SAP_BI 3.5 Net Weaver 04 SAP PIB 2005_1_640 SAP_ABA, 6.40 SAP_BASIS, 6.40 SAP Kernel 6.40
e.g. disp+work, R3trans, tp, R3load
SAP KW 7.0
30
Which Type of Support Package to use with NW04s BI

WP-PI 6.00 is Integrated in the Basis PI (PIB) From 7.00 Base System the R/3 PI is integrated in ECC 6.0
This is also valid for ERP2005
Dependencies of Support Packages
XI is now integrated as PI in the Abap and Java Stack of Netweaver 04s BI 7.0 is part of the Netweaver 04s Stack The SAP PIB is integrated with the Netweaver Stack New with Basis 7.00 is the integration of the R/3 PI into ECC
SAP SPAM/SAINT 7.00 ECC 6.0 BI BC 7.x SEM 6.0 FIN 6.0 PI 7.0
SAP_BI 7.0 Net Weaver 04s SAP PIB 2005_1_700 SAP_ABA, 7.00 SAP_BASIS, 7.00 SAP Kernel 7.00
e.g. disp+work, R3trans, tp, R3load
SAP KW 7.0
31
BI as dormant coding in ERP2004/5 (if wanted)
If you not want to use the BI Function, lock the AWB and add a value for the field BWMANDT in Table RSADMINA. See also Note 122679 for Details.
Special Considerations for BI:

Check the details for the Usage of BI together with Oracle that the table space PSAPTEMP is from type temporary. If you want to use additional table spaces for BI for Fact tables, ODS objects and Dimension tables please check note 552911 and 502989 for details.
PSAP<SID>ODS PSAP<SID>FACT PSAP<SID>DIM
After the initial Setup of SAP NetWeaver 2004s there is only a an initial Configuration Profile available which does not met the BI/OLAP requirements. So the consulting of the following notes is a mandatory step before the use of the BI application. Note 192658 - Setting basis parameters for BW Systems Note 830576 - Parameter recommendations for Oracle 10g Note 702728 - Profile parameter for export/import buffer instances Note 656060 - OLAP: Cache main memory displacement not functioning Note 480710 - Profile parameters for table buffers Note 928044 - BI lock server With the table RSADMIN you can do additional DB settings.
32
Remove logical system for BI (if wanted/needed)
If you activated the BI functionality on the ERP2004 not by purpose, and you want to rid of the my SAP BI system use the Function RSAR_LOGICAL_SYSTEM_DELETE and keep Destinations and Declarations. See Note 140276 for Details.
33
Check for additional Functions on the source System

If you want to use the BI Function within ERP2004 you may check Settings like Transfer Global Settings or Transfer Exchange Rates if they are available.
34
Check EDIDOC Number Range for outbound (ECC)

During the manual/automatic connection of the ECC source system to the BI system the Number Range might not be available in the ECC client. Note: Number Ranges are client depended. See also Note 522569 for more Details about different clients in one BI System.
35
Check for a valid ALEREMOTE user to source System

See more Details in Note 538052 about the Myself destination in BI. Still the correct Source System connection needs a valid ALEREMOTE user with the right profile. OLAP BI system S_BI-WHM_RFC S_BI-WHM_SPC OLTP R/3 system S_BI-WX_RFC S_BI-WX_RFCA
36
Oracle technical Background

The Oracle database system has different performance tuning options for different purposes
Typically, OLTP based systems (SAP ECC) and OLAP systems (SAP BI) have conflicting performance optimization goals
If OLTP and OLAP systems both use the same Oracle instance, a compromising set of parameter settings needs to be defined
Make sure that the Partition Option is installed when upgrading or Installing ERP2004/5 together with Oracle
37
Recommendations for Oracle Database

An Oracle instance running both OLAP and OLTP systems must have parameters set according to SAP note 632556. In addition to the parameters described in this note, the following settings are mandatory (i.e. need to be added or replace parameters in the note):
workarea_size_policy = AUTO pga_aggregate_target = 20-40% of available RAM db_file_multiblock_read_count = 16 optimizer_index_cost_adj = 50 hash_join_enabled = TRUE event = 10183 trace name context forever, level 1 star_transformation_enabled = TRUE
It is also mandatory to create DB CBO statistics with brconnect only (do NOT use ANALYSE TABLE statistics!)
38
Recommendations Oracle 10g only

We recommend to upgrade to Oracle 10g as soon as possible to benefit from optimizer improvements which are likely to minimize any side effects caused by the mixed-mode parameterization. For obsolete Parameters with Oracle 10g please check Note 830576:
_b_tree_bitmap_plans = false _optim_peek_user_binds = false _eliminate_common_subexpr = false fast_start_mttr_target = 900 hash_join_enabled = true log_archive_start = true optimizer_max_permutations = 1500 optimizer_mode = all_rows (Default) statistics_level = typical timed_statistics = true transaction_auditing = FALSE
39
Other Databases
DB2/DB6 uses similar techniques like Oracle. Therefore you might also a compromising set of parameter settings needs to be defined. MaxDB in the Version 7.5 and 7.6 is delivered as the OLTP Version only. The Settings for OLAP Systems, like BI are also valid for OLTP Systems like ECC. For the usage of MS SQL together with SAP Applications there are no special settings either for OLTP or OLAP. The Database handles both types the same way.
40
Upgrade to ECC 5.0 or higher from lower R/3 Release

If you Upgrade your R/3 System like described in the Section Deployment Option for Example from:
R/3 3.1I to ECC 5.0/6.0 R/3 4.0B to ECC 5.0/6.0 4.7 Enterprise to ECC 5.0/6.0
only the Fix for ECC 5.0/6.0 from the Note 663240 is necessary. There is no influence on the BI components. These components will be activated separately in a later step. If there is also a J2EE Engine available please make sure that this is connected to the BI Client for the usage of BI_MMR and BI_UDI. The EP is connected to this Client also. If you want to use the J2EE Engine also for the ECC Component you need an additional J2EE Engine.
41
Any Questions?
If you have further questions, please contact Rainer Uhle (rainer.uhle@sap.com) or Roland Kramer (roland.kramer@sap.com)
nt ulta ons yC
lg hno r me er tec ra av e dK lan NetW G Ro ior )A en eiz S hw e 80 rf Sc o P ( strass ensd SA ard eg R 2 Alth 8105 660 HC 871 8418 ) (58 15 12 om +41 (79) 2 71 61 sap.c T 41 8 ) r@ M + 41 (58 rame + d.k F olan E r
42

WDEBU7 BI and ECC in One System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WDEBU7 BI and ECC in One System

Uploaded by

Copyright:

Available Formats

WDEBU7 Workshop Chapter 08 NW 2004(s) BI and ECC Deployment Options

Roland Kramer Rampup Coach nw2004s SAP Switzerland

NW 2004(s) BI and ECC (Core) Deployment Options

Introduction mySAP ERP Deployment Options Installation Scenarios Technical Remarks

NW 2004(s) BI and ECC (Core) Deployment Options

Introduction mySAP ERP Deployment Options Installation Scenarios Technical Remarks

The challenge of Sizing and Designing

SAP Enterprise Core Components (ECC)

SAP Clients SAP Clients DBs, DB Schemas DBs, DB Schemas

OLTP OLTP OLAP OLAP Servers Servers Networks Networks

SAP NetWeaver 2004(s) SAP NetWeaver Business Intelligence

Database Management System

MCOD MCOD MCOS MCOS

DBSL, ODBC, JDBC DBSL, ODBC, JDBC

SAP AG 2003, Title of Presentation, Speaker Name / 4

Growing Complexity vs. TCO Reduction

Hardware Costs Implementation Costs Operation Costs

SAP AG 2003, Title of Presentation, Speaker Name / 5

SAP AG 2003, Title of Presentation, Speaker Name / 6

Our Costs of Development

The true costs are the full lifecycle costs

Complexity is the main cost driver

Poor quality erodes profitability

NW 2004(s) BI and ECC (Core) Deployment Options

Introduction mySAP ERP Deployment Options Installation Scenarios Technical Remarks

mySAP ERP Running on Top of SAP NetWeaver

System 1: SAP NW 04 and SAP ECC in One System

Separate System 2: SAP NetWeaver 04 running XI Clients

SAP NetWeaver 04 running BI, EP

KMC Portal Platform

KW Functionality KW Functionality KW Functionality Web AS ABAP Web AS Java

SAP AG 2003, Title of Presentation, Speaker Name / 9

SAP ECC 5.0 mySAP ERP 2004

SAP ECC 5.00 is the central component of mySAP ERP 2004

SAP ECC 5.0

Add-On Add-On Add-On

Making full use of SAP NetWeaver

SAP ECC Core Add-On SAP NetWeaver `04 BI-BC

SAP AG 2003, Title of Presentation, Speaker Name / 10

SAP ECC 6.0 mySAP ERP 2005

SAP ECC 6.0

Former Add-On Former Add-On Former Add-On Former Add-On BI-BC

SAP ECC Core SAP NetWeaver 2004s

SAP AG 2003, Title of Presentation, Speaker Name / 11

NW 2004(s) BI and ECC (Core) Deployment Options

Introduction mySAP ERP Deployment Options Installation Scenarios Technical Remarks

Deployment Options with mySAP ERP

SAP R/3 4.6C

SAP R/3 4.6C

SAP ECC NW04 BI

Deployment Options with mySAP ERP (cont.)

SAP R/3 4.0B

SAP ECC NW04 BI

+ Add. functionality provided by SAP R/3 Enterprise

- Higher effort (both upgrades in same timeframe)

Deployment Options with mySAP ERP (cont.)

SAP ITS SAP R/3 3.1I SAP ITS SAP R/3

SAP ECC SAP ITS

SAP ECC NW04 BI Upgrade, SAP ITS implement

NW 2004(s) BI and ECC (Core) Deployment Options

Introduction mySAP ERP Deployment Options Installation Scenarios Technical Remarks

Installation Scenarios: Shared nothing concept

Box 1 Operating System WAS Application

Oracle DB Schemas ABAP/J2EE