WDEBU7 BI and ECC in One System

1

WDEBU7 WorkshopChapter 08

NW 2004(s) BI and ECC Deployment OptionsRoland Kramer Rampup Coach nw2004s SAP Switzerland

2

Deployment Options

Installation Scenarios

Introduction

mySAP ERP

Technical Remarks

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

3

Deployment Options


Introduction

mySAP ERP

Technical Remarks


4

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

The challenge of Sizing and Designing

TCO + ROITCO + ROI

SAP Enterprise Core Components (ECC) Financials SCMHCM…

SAP NetWeaver 2004(s)SAP NetWeaver Business IntelligenceSAP NetWeaver Application Server….

OperatingSystem

Database Management System

DevelopmentTesting

Production

DevelopmentTesting

Production

MCODMultiple Components One DB

MCOSMultiple Components One

System

MCODMultiple Components One DB

MCOSMultiple Components One

System

ApplicationsPlatformsDBMSsOperating Systems

ApplicationsPlatformsDBMSsOperating Systems

ServersNetworks

ServersNetworks

SAP ClientsDBs, DB Schemas

SAP ClientsDBs, DB Schemas

DBSL, ODBC, JDBCDBSL, ODBC, JDBC

Client-ServerESA

Client-ServerESA

OLTPOLAP

OLTPOLAP

SAP DDICDB Repository

SAP DDICDB Repository

5


Growing Complexity vs. TCO Reduction

R/3

SAP R/3

PLMERPSRMCRM

AnalyticsNetWeaver

R/3

Hardware Costs Implementation CostsOperation Costs

mySAP Business SuiteSCM

6


TCO Drivers

HardwareToo many serversNo joint resource utilizationOversized system landscape

ImplementationDifferent implementation guidelinesMultiple independent and overlapping customization systemsComplex Customizing (x100,000 customizing parameters)No end-to-end process verificationMassive testing effort

OperationsNo unified system managementComplex multi-component dependencies Error prone cross-component system integrationCostly cross-system change management

7


Our Costs of Development

The true costs are the full lifecycle costs

Maintenance costs by far exceed initial development costsThe value/effort ratio for development decreases over lifetimeCosts multiply with the combination of multiple releases and multiple components that have to be maintained

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 fixOnly quality per design leads to scalable business

Complexity is the main cost driver

Complexity drives cost growth exponentiallyThe number of one-to-one integrated system components increases complexity Complexity management is an architectural problem

8

Deployment Options


Introduction

mySAP ERP

Technical Remarks


9


mySAP ERP Running on Top of SAP NetWeaver

System 1: SAP NW ’04 and SAP ECC in One System(BI and ECC in different clients)

ECC BP ESS/MSS

SAP

ECC

System 2: SAP NetWeaver ’04 running XI

ABAP JavaDatabase

ABAP StackAdditional

Components

J2SE Adapter

Adapter Engine

Java Stack

KW FunctionalityKW FunctionalityKW Functionality

MI FunctionalityMI FunctionalityMI Functionality

XI Functionality

BI FunctionalityBI FunctionalityBI Functionality

Web AS ABAP

XI

Web AS Java

ABAP JavaDatabase

ABAP StackAdditional

Components

TREX

BI AnalyPrec Serv

Java Stack

SAP

Net

Wea

ver ’

04 ru

nnin

g B

I, EP

KW FunctionalityKW FunctionalityKW Functionality

MI FunctionalityMI FunctionalityMI Functionality

XI FunctionalityXI FunctionalityXI Functionality

BI Functionality

BI Content

Web AS ABAP

KMC

BI Java Components

Web AS Java

Portal Platform

Adobe DS

Front End

Web Browser

SAP GUIw/ BI Ext

Front End

Separate Clients

Separate Clients

10


SAP ECC 5.0 – mySAP ERP 2004

SAP ECC 5.00 is the central component of mySAP ERP 2004 (ECC = ERP Central Component)

Making full use ofSAP NetWeaver

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.

A

Add-On

Add-On

Add-On

Add-On

BI-BC

SAP ECC Core

SAP ECC 5.0

SAP NetWeaver `04

EE EE EE

Extension Sets

11


SAP ECC 6.0 – mySAP ERP 2005

FormerAdd-On

SAP ECC Core

FormerAdd-OnFormerAdd-OnFormerAdd-On

BI-BC

SAP ECC 6.0

SAP NetWeaver 2004s

EE EE EE IE IE IE

Enterprise & Industry Extensions

Industry solutions shipped in my SAP ERP 2005 are technically realized:

within the cross-industry application’s Coreas Industry & Enterprise 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!!)as Add-Ons -> Only these few remaining industry-specific applications are shipped separately and carry their own releaseor as a combination of the above-mentioned possibilities

C

IE

A

12

Deployment Options


Introduction

mySAP ERP

Technical Remarks


13


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:

SAP R/34.6C

+ No effort required for SAP R/3 upgrade

+ Immediate start of BI implementation

SAP R/34.6C

NW04 BI

Stay Install and implement

- SAP R/3 upgrade still required by 2006

Option A:

SAP R/3 Enterprise NW04

BI

Upgrade Install and implement

+ Add. functionality and benefits provided by SAP R/3 Enterprise

+ Longer mainstream main-tenance for SAP R/3 Enterprise

- Higher effort (upgrade and implementation in same time frame)

Option B:

* These are examples only. More options might be available to the individual customer

SAP ECC

NW04 BI Upgrade and

implement

+ Add. functionality and benefits provided by SAP ECC

+ Lower TCO through integrated BI

Option C*:

- Resizing of server landscaperequired

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 pointPossible 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.

14


Deployment Options with mySAP ERP (cont.)

Target: Customer wants to benefit from the business intelligencecapabilities provided by mySAP ERP

Today: Customer operates SAP R/3 4.0B and SAP BW 3.0B/3.1

SAP R/34.0B

SAP BW3.0B/3.1

Today:

SAP R/3Enterprise

SAP BW3.0B/3.1

Upgrade Stay

+ Add. functionality provided bySAP R/3 Enterprise

- End of maintenance for SAP BI3.0B is December 31, 2006

- Functionality in SAP BW is stilllimited to SAP BW 3.0B

Option A:

SAP ECC NW04BI

Upgrade Upgrade

+ Add. functionality provided bySAP ECC

+ Long maintenance for SAP ECC and SAP BI

- Higher effort (both upgrades in same timeframe)

Option B:


SAP ECC

NW04 BI Upgrade and

migrate SAP BI


+ Lower TCO through integrated SAP BI

Option C*:


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 doesn’t want to enter customer specific maintenance.

15


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

SAP R/33.1I SAP ITS

Today:

SAP R/3Enterprise

SAP ITS

Upgrade

Stay/upgrade

NW04 BI

Install and implement

+ Add. functionality provided bySAP R/3 Enterprise

+ Long maintenance (SAP BI and SAP R/3 Enterprise)

- Upgrade to SAP ITS might be required

- Higher TCO

Option A:

SAP ECC NW04BI

Install and implement

SAP ITSUpgrade

and migrate

ITS


+ Longer maintenance + Utilization of integrated ITS

- Customer needs to wait until SAP ECC becomes available

- SAP BI still requires own system

Option B:


SAP ECC

SAP ITSNW04 BI

Upgrade, implement

BI and migrate

ITS


+ Longer maintenance + Utilization of integrated SAP

BI and SAP ITS

Option C*:


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.

16

Deployment Options


Introduction

mySAP ERP

Technical Remarks


17


Box 2Box 1Operating SystemOperating System

WAS

Installation Scenarios: Shared nothing concept

ApplicationSAP ECC

Clients 008, 009, …

Oracle DBSchemas

ABAP/J2EESAP ECC

WAS

ApplicationSAP BIClient 011

Oracle DB

Schemas ABAP/J2EE

SAP BI

Todaysmost often Installed Scenario

Todaysmost often Installed Scenario

Load

OLAPOLTP

=

ABAP/JAVADBSL/JDBC

ABAP/JAVADBSL/JDBC

18


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

Cons

Too many boxes?

Risk of Network traffic?

Administration efforts?

Does SAP NetWeaver 04give good reasons to

change running installations?

Does SAP NetWeaver 04give good reasons to

change running installations?

… normallynot really …

19


Scenarios, Principles, Procedures …

MDMP – Multiple Display Multiple ProcessingSeveral Codepages are used with the same Database

Note 745030 MDMP - Unicode Interfaces: Solution Overview

MCOD – Multiple Components One DatabaseSeveral components share the same Database

Note 712777 MCOD operation of R3 and BI in a database

MCOS – Multiple Components One SystemSeveral components share the same Database Schema

Note 855534 Embedded NetWeaver Components in ERP

… SAPTerminology

… SAPTerminology

20


Box

Operating System

Oracle DB

NW AP 2

ApplicationSAP BIClient 011

ABAP/JAVADBSL/JDBC

NW AP 1

ApplicationSAP ECC

Clients 008, 009, …

ABAP/JAVADBSL/JDBC

OLAPOLTP

Scenario MCOD: Multi Components One Database

Two WAS onOne box

* Session oriented settings for OLAP based systems like BI

Schemas ABAP/J2EESAP ECC

Schemas ABAP/J2EE

SAP BI… getting one

DB instance with several schemas

using logon Trigger*

… getting oneDB instance with several schemas

using logon Trigger*

21


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 start from the scratch,

but how do you handle the reorganization of your

system landscape in case of growth …?

Might be an option if you start from the scratch,

but how do you handle the reorganization of your

system landscape in case of growth …?

22


Box

Operating System

Scenario MCOS – Multiple Components One System

Oracle DB

Schemas ABAP/J2EESAP ECC/BI

NW AP

ApplicationSAP ECC/BI

Clients 008, 009, …, 011

ABAP/JAVADBSL/JDBCOLTP/

OLAP

… one DB Schema. Logon Trigger* are

not possible

… one DB Schema. Logon Trigger* are

not possible

One WAS withseveralClients

* Session oriented settings for OLAP based systems like BI

23


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

ERP 2005

Operating System

DI ABAP DI JAVA

CI JAVA

000JAVAJDBC

J2EE 7.00

CI ABAP

000, 001, 002, 066

ABAPDBSL

ECC/BI

SchemaABAP

SAP<SID>

Schema JAVA

SAP<SID>DB

SCS Manager

SLD

SLM

NWA

BI-Java

EP

Selected JavaApplications:

ESS 2005

01 02

03

24


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 CPU‘s for this single box

Prices for servers are increasing supra linear (faster) with the number of CPU‘s

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 start with BI in a small

scenario. You will switchASAP to separate Boxes.

Might be an option if you start with BI in a small

scenario. You will switchASAP to separate Boxes.

25

Deployment Options


Introduction

mySAP ERP

Technical Remarks


26


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 MCOSconfiguration. See also Note 747036.

27


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.

28


Note the dependences between ECC and BI

29


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

30


Which Type of Support Package to use with NW04 BI

SAP Kernel 6.40

SAP_BASIS, 6.40

SAP_ABA, 6.40

ECC 5.0

SAP SPAM/SAINT 6.40

SEM4.0

R/3 PI 2004.1

e.g. disp+work, R3trans, tp, R3load

SAP PIB 2005_1_640

FIN 3.0

New with Basis 6.40 is the integration of the other PI’s like WP-PI in the Basis PI

Up to 6.40 Base System every R/3 based system needs the R/3 PI

SAP KW

7.0

BI 3.5 is part of the Netweaver 04 Stack

WP-PI 6.00 is Integrated in the Basis PI (PIB)

SAP_BI 3.5

BI BC 3.5.x

XI 3.0

NetWeaver

04

This is also valid for ERP2004

The SAP PIB is integrated with the Netweaver Stack

Dependencies of Support Packages

31


Which Type of Support Package to use with NW04s BI

SAP Kernel 7.00

SAP_BASIS, 7.00

SAP_ABA, 7.00

ECC 6.0

SAP SPAM/SAINT 7.00

SEM6.0

e.g. disp+work, R3trans, tp, R3load

SAP PIB 2005_1_700

FIN 6.0

New with Basis 7.00 is the integration of the R/3 PI into ECC

From 7.00 Base System the R/3 PI is integrated in ECC 6.0

SAP KW

7.0

BI 7.0 is part of the Netweaver 04s Stack

WP-PI 6.00 is Integrated in the Basis PI (PIB)

SAP_BI 7.0

BI BC 7.x

PI 7.0

NetWeaver

04s

XI is now integrated as PI in the Abap and Java Stack of Netweaver 04s

This is also valid for ERP2005

The SAP PIB is integrated with the Netweaver Stack

Dependencies of Support Packages

32


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.

33


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.

34


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.

35


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.

36


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

37


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

38


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 = AUTOpga_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 1star_transformation_enabled = TRUE

It is also mandatory to create DB CBO statistics with brconnect only (do NOT use ANALYSE TABLE … statistics!)

39


Recommendations – Oracle 10g only

We recommend to upgrade to Oracle 10g as soon as possible to benefit from optimizer improvements which are likely to minimizeany side effects caused by the mixed-mode parameterization.

For obsolete Parameter’s 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 = 900hash_join_enabled = truelog_archive_start = trueoptimizer_max_permutations = 1500optimizer_mode = all_rows (Default)statistics_level = typicaltimed_statistics = truetransaction_auditing = FALSE

40


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.

41


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.0R/3 4.0B to ECC 5.0/6.04.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.

42


Any Questions?

If you have further questions, please contact

Rainer Uhle ([email protected]) or

Roland Kramer ([email protected])

Roland Kramer

Senior NetWeaver technolgy Consultant

SAP (Schweiz) AG

Althardstrasse 80

CH-8105 Regensdorf

T +41 (58) 871 6602

M +41 (79) 215 8418

F +41 (58) 871 6112

E [email protected]

WDEBU7 BI and ECC in One System

Documents

Transcript of WDEBU7 BI and ECC in One System