BI connection with ECC

Question

Hello BI experts,
Iam BASIS guy and working on SAP R/3 4.72 to ECC6 upgrade project.I have few tasks which is related to BI7.0 & source systems
Let me put like this current landscape
SAP R/3 4.72 -  DVE               QAS          PRD
SAP BI7.0          BD1               BQ1           BWP
Now we are upgrading SAP R/3 4.72 to ECC6 in seperate hardware in parallel ladscape.Copy DVE to another system and different SID ( EC1 ), QAS to (EQ1) and PRD upgrading on same hardware.
So we will have to maintain two landscape parallely till live.And then we will break old source system SAP 4.72 and continue with new systems ECC.
I know as per SAP best practice we need sepearte BI landscape for upgrade landscape instead of same hardware.But customer can not spend money for new hardware and they wanted to go with same hardware.
I will Integrate BD1 to new source system EC1 and similar to QA, but after creating this source system I can see duplicate two source systems , one old and another new. And again 2 info packakeges and 2 process chains and etc..
How we can handle such type of landscapes? Do we need any BI manual activites? and how much effort we have to put?
Your expert solutions greatly appriacted?
- Jim

Answer 1

Hi,
Creating Source System (SALE): This step creates source systems which are to be connected.
1.
Assigning Source System to Client (SALE): This step gives a logical name to a SAP Client from which the communication is to be established.
2.
Setting up RFC Destination (SM59): This step is required to establish remote connection to the partner with which Source system is trying to communicate. Here one has to maintain the logon and IP details of the target system.
3.
Distributing Data Model (BD64): A distribution model is used to model a distributed environment in which you specify messages exchanged between sending and receiving systems. Here one has to define the message protocols with which the two systems will communicate.
4.
Generating Partner Profile (BD82): This process generates a partner profile for each system with which your system communicates. Outbound records are created in the partner profile for each outgoing message, and inbound records are created for each incoming message.
Note: If one distributes Data Model before generating partner profile then one has to redefine partner profile in other system also (repeat step in both system). In this document we are generating partner profile after Distribution of data model so as to demonstrate how to maintain inbound and outbound message types in WE20.
5.
Maintaining Message Types (WE20): This process is optional. Generally while generating partner profiles we automatically get the respective Outbound and Inbound messages, which can be checked in T-Code WE20. If the message types are not defined then one can manually do it by following this process.
These steps will ensure that the BW and other source systems are in sync and will communicate as expected.
SAP COMMUNITY
Step 1: Define Logical System in R/3
Step 2: Assigning Logical System to Client
Step 3: Setting Up an RFC Destination
Step 4: Distributing Data Model
Message Types Involved in Process of Data Loading
Step 5: Generating Partner Profile
Step 6: Maintaining Message types in T-Code WE20
Regards,
Suman