Source System Connections

Contents:
BW and Source System Connections RFC Connections Plug-In Installation

SAP AG 1999

Source System Connections: Unit Objectives

At the conclusion of this unit, you will be able to:

Describe the SAP strategy for system interface

Plan the installation of the R/3 Plug-In Describe interface strategies in designing system landscapes

SAP AG 1999

Connecting BW to R/3 Source Systems

BW
R/3

Checklist

Define user ALEREMOTE in BW and R/3 Define new Source system Check RFC Connection with remote Logon Replicate DataSources Check/Transfer of global Settings Map Source System Names Maintain Control Parameters for Data Transfer

R/3, BW => /nsu01 BW => Admin WB BW => Admin WB BW => Admin WB BW => Admin WB BW => Admin WB R/3 => /nsbiw

SAP AG 1999

Create Source System

RSA1 => Source Systems Context Menu Choose create Choose system type

For a typical R/3 system, choose automatic creation

SAP AG 1999

Connecting R/3: Create Source System

Provide R/3 hostname

use central instance

Give <SID>, system number

BW and R/3 RFC users should already exist

passwords must be known

user is ALEREMOTE in both

BW and R/3

SAP AG 1999

Verify & Add Authorizations to the RFC users

R/3 RFC user: S_BI-WX_RFC

Add to R/3 RFC user: B_ALE_ALL S_IDOC_ALL R/3 Source System

BW System

BW RFC user: S_BI-WHM_RFC SAP_ALL SAP_NEW S_RS_ALL

SAP AG 1999

Source System Connections: Some facts

A BW system can serve as a source system for another BW system. This scenario is referred to as a data mart.

The ODS can be a DataSource for another BW system.

An InfoCube can be a DataSource for another BW system. A BW system can be a source system for an APO system.

An APO system can be a source system for a BW system.

Two-way data exchange is possible.

BW can be a source system for other SAP strategic initiative products, such as SEM and CRM

SAP AG 1999

Mapping of the Source System Names

Maintain entries for ALL systems in the BW landscape.

SAP AG 1999

Replicate Source System DataSources

Replicate DataSources
is the means by which R/3 application metadata becomes available within the BW system.

SAP AG 1999

Maintain data packet size in source system

Allows tuning of packet sizes (table ROIDOCPRMS)

Optimal settings depend upon network configuration. IDOC packet sizes between 20000 and 50000 are recommended. Frequency represents the threshold to send statistical information = 10.

Max proc. is the maximum number of parallel extraction processes. This setting is a function of the number of CPUs and configured BTC processes.

SAP AG 1999

Transfer Global Settings from Source System

SAP AG 1999

System Copy possibilities

The recommended method is to maintain systems using the Transport Management System rather than doing a database copy. If a BW system is copied, source systems and source system-dependent objects must be maintained.
Generally, a source system is deleted in the copied BW system, and a connection is established to a new source system. Source-system specific objects need to be transported in order to avoid re-configuring manually.

SAP AG 1999

R/3 Plug-Ins: Overview

Other SAP Applications

SAP R/3 System

Integrates an R/3 system with other SAP Applications

Pre -requirements are sometimes release-specific

HP/LCP levels Basis packages

Patches for R/3 Plug-Ins exist via SAPnet NDAI is the former term used with R/3 Plug-Ins
Acronym for New Dimension

Application Integration

See SAPnet/R3-Plug-In for information on R/3 Plug-Ins!

SAP AG 1999

R/3 Plug-In Overview

SAP will ship two R/3 Plug-In releases each year starting in 2000:

PI 2000.1, available in the second quarter of 2000 PI 2000.2, available in the fourth quarter of 2000)

R/3 Plug-Ins will be constantly enhanced

Ensure integration between a given R/3 standard release and the different versions of SAP Applications.

include latest functionality.

Two types of R/3 Plug-Ins exist:

Modifying: means some R/3 objects may be modified during R/3 PlugIn installation. Modification-free: means that no R/3 objects are modified during R/3 Plug-In installation.

SAP AG 1999

R/3 Plug-In Overview: R/3 Plug-In Version PI

R/3 Plug-In version PI Contains extraction programs for all SAP strategic initiative applications: BW, APO, BBP, CRM, and SEM
PI is a modifying R/3 Plug-In:
PI 99 is modifying for R/3 versions between 3.1h and 4.6A. PI 2000.1 is modifying for only for R/3 versions 3.1h and 3.1i. This means a Conflict Resolution Transport will likely be required when installing the R/3 Plug-In.

PI is a modification-free R/3 Plug-In :

PI 99 is modification-free for all R/3 version 4.6B.
PI 2000.1 is modification-free for all R/3 versions 4.0B and higher.

SAP AG 1999

R/3 Plug-In Overview: R/3 Plug-In Version PI-A

R/3 Plug-In version PI-A contains extractors for BW only.

No other extraction programs are included for APO, SEM, etc.

PI-A is Modification-free
This type R/3 Plug-In has served to provide interfaces for BW systems, when no modification has been possible for R/3 objects. SAPs R/3 Plug-In strategy has changed, so that all future R/3 Plug-In versions of PI are to be modification-free.

PI-A validity:

PI-A 99 (BW 1.2B and 2.0A) for R/3 release 3.1H - 4.5A. PI-A 2000.1 (BW 2.0B) for R/3 releases 3.1H and 3.1I only.

SAP AG 1999

R/3 Plug-In information: Versions

PI-A/31H PI-A/31I

*
PI/31H PI/31I

SAP AG 1999

R/3 Plug-Ins

R/3 Plug-Ins are Backwards compatible with previous release of the R/3 Plug-In.

R/3 Plug-In releases can be installed without requiring changes to existing settings/processes. Example: PI 2000.1 can be installed on an R.3 system that has PI 99 already installed.

R/3 Plug-Ins are Backwards compatible with the next-previous release of the SAP Applications.

The previous release of the SAP Application can continue to be used after an upgrade of the R/3 Plug-In Example: BW 2.0A can be used with PI 2000.1

Older versions of the R/3 Plug-In is not upward compatible with new versions of SAP applications

An older R/3 R/3 Plug-In release (i.e. PI 99) can not be used with a new SAP Application release (i.e. APO 3.0A).

SAP AG 1999

R/3 Plug-In information for R/3 upgrades:

When upgrading the R/3 system it is important to consider R/3 Plug-Ins! A R/3 Plug-In upgrade CD is necessary when upgrading the R/3 version.
During an R/3 upgrade, the R3up script will stop and ask for the R/3 Plug-In upgrade CD This keeps extraction programs active and upgrades their version. Do not ignore this phase - the extraction programs may be deleted. Plan ahead to have required CD available.

SAP AG 1999

R/3 Plug-In Installation- Facts

R/3 Plug-In installation looks like a mini R/3 upgrade

uses R3up utility, Upgrade Assistant

R3up script is standard - requires all objects locked in repairs to be released

This is true even for the non-modifying R/3 Plug-Ins, PI Prior to R/3 Plug-In installation: find locked objects (Se03, Se13)

R/3 Plug-In installation will import latest versions of extractor programs and DataSource structures

old extraction programs are overwritten!

Cases of customization to standard extraction programs:

SAP AG 1999

R/3 Plug-In Installation

As of R/3 Plug-In version 2000.1, and R/3 version 4.6B, R/3 Plug-Ins are no longer installed using R3up. Instead, the Add-on installation tool SAINT is used for R/3 Plug-In installation. Transaction: SAINT

SAP AG 1999

R/3 Plug-In Installation

Check the R/3 Release and run the Program startup.exe. Make sure that you give the R/3 Release in the CD Path. The Upgrade Assistant or Scroll Mode can be used.

SAP AG 1999

R/3 Plug-In Installation Reminder 1

Check the R3up keyword (See Notes).

R3up will stop the running R/3 System.

R3up will demand that objects locked in repairs are released.

SAP AG 1999

R/3 Plug-In Installation Reminder 2

Example: Extend the suggested Tablespace according the error.

SAP AG 1999

BW Installation - Finishing Add-On Installation

The transaction SPAU can be run after the R3up process is complete. Check the R/3 System after Installing the Add-On like an R/3 Upgrade.

SAP AG 1999

R/3 Plug-Ins - Download Add-On Support Packages

Available on SAPnet alias ocs-download
Download Support Packages

Add-On Support Packages/CRTs New Dimension Applications/R/3 Plug-Ins

PI-A, PI R/3 Plug-In Support Packages

SAP AG 1999

Source System Connections: Unit Objectives

Now you are able to:

Describe the SAP strategy for system interface

Plan the installation of the R/3 Plug-In Describe interface strategies in designing system landscapes

SAP AG 1999