How do we connect ECC with BW/BI

Let me give you the brief idea about ECC and BI first before learning about connectivity between ECC and BI. ECC is a business application software in which users will input the business data on daily basis. Total data will be stored in a database. Enterprises use not only ECC but also other source systems like CRM, SCM and SRM in which the business data will be inserted by different types of users on daily basis. Each data will be stored in different types of databases either homogeneous or heterogeneous RDBMS’s. We need to have a tool to extract the data from these source systems. BI is a software which is developed by SAP to extract data from these source systems for further analysis. We have to connect each source system to BI to get his data extraction.

There are two names to BI. They are BW and BI. What is the difference between BW and BI. Let me give you a clear idea. BW is SAP BW which is only SAP Data Warehouse. BW is being called by the name of SAP BW up to version 3.5. The name has been changed to SAP BI From version 7.0 onwards. BI refers not only Data Warehouse, but also a complete set of products which are all provided by SAP to build the Business Intelligence system.

SAP Business Information Warehouse (BW) is also a one of the data warehousing system which provide the kind of decision making support system that is needed in today’s enterprise business environment.

To connect BI System with ECC….

You should install ECC and BI either in separate boxes or in single system as virtual machines using VMware or Virtual PC. You can install both systems in single system if you want to practice at home. BI system sends a request in the form of a  intermediate document (IDoc) to the SAP source system R/3. Then the SAP source system extract the data and sends it to the BI system. The two systems exchange additional information like information about extracted data, data source details, data package number and number of records in the form of IDocs

Step-by-step procedure to connect BI with ECC…

  • Define the logical system in R/3 using the transaction code SALE in both the systems (ECC and BI)
  • Assign Logical System to a client using transaction code SCC4 in both the systems (ECC and BI)
  • Setup the RFC Destination using transaction code SM59 in both the systems (ECC and BI)
  • Hit Transaction BD64 and Click Create model view –  Enter the Short text – Enter the Technical name  – Hit Execute –  Distribution Model will be created and the technical name of the distribution model will be listed
  • Place the cursor on model created and and click Add message type button on the top right corner
  • Enter sender and receiver system IDs  and select the correct message type assigned to the correct system
  • Distribute this model using Edit – Model View – Distribute
  • Select the receiver of the model view and proceed to distribute the model
  • Please note that the distribution of data model is not required to repeat in BI system as this step automatically replicates settings in BI
  • You have to generate partner profile for each system with which your system communicate using BD82
  • Outbound records are created in the partner profile for each outgoing message and inbound records are created for each incoming messages
  • You can view the partner profiles generated using the transaction code WE20

Message Types:

  • RSRQST: This message type is send by BI to R/3 while loading any data. This gives information about the data source, selection condition and other BI settings to R/3.  As and when a load is started in BI, RSRQST message type is sent to R/3 requesting for data.
  • RSINFO: Once R/3 receives RSRQST message from BI, it sends an acknowledgment message type to BI informing about the status of the request. That is whether the request can be handled or not by R/3. It also gives information about how many data packages are being send and what is the total number of records extracted for the given data source and selection.
  • RSSEND: After sending a positive acknowledgement to BI, R/3 starts the extraction job and starts collecting data in data IDocs. This message type carries the actual data with it into the BI system.
(Visited 3,957 times, 2 visits today)

6 Comments

  1. Prakash E

    Hi Raj,

    Thanks for sharing the information , i am currently trying to load Data frm ECC to SAp BW .

    Regards
    E.Prakash

    Reply
  2. Venezolano

    Sin duda lo que has publicado me ha resultado de utilidad.
    Si bien tengo que decir que algún otro post distinto no me resultó tan
    interesante, lo de esta vez me ha interesado realmente.

    Un saludo

    Reply
  3. zahoor

    Hi Raj,

    Thanks lot for correct information about ecc and bi connectivity .. but i have some queries regarding steps;
    1) in which system ECC OR BI we will hit BD64
    2) in system ECC and BI which system will be sender and which will be receiver ..
    3) In which system we have to assign which message type out of three.
    4) while distribution which logical system we have select as a receiver?
    5) how we can generate partner profile please explain by step.
    6) is there any things left in BI system by using RSA1 code?

    Reply
  4. Richa

    Hi Raj

    Thank you for the above information.

    I am trying to learn SAP BI and had a query in it.
    I wanted to extract data from BI to ECC ie the reverse way
    Can you please tell me how should I do that.

    Would be grateful if you could guide me.

    Thank you

    Richa

    Reply
  5. Manish

    Hi Raj,

    First of all, thank you so much for putting the above in.

    I am very new to SAP and am trying to learn SAP BI and BASIS. I have a really basic question.

    I have managed to install SAP IDES with Ecc6 and BI 700. I have read what you have written and what many others have written but I still don’t understand how I can get data in my BW system from ECC6.

    Would appreciate if you can guide me / point me to some useful documentation.

    Regards,

    Manish Danani

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *