RFC connection BI and ECC 6.0

Hi
I am trying to connect BI and ECC 6.0 at home on two different virtual machines for data extraction and practicing delta management ( they are on the same virtual network).
I am following these steps :
Step-by-step procedure to connect BI with ECCu2026
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 u2013 Enter the Technical name  u2013 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 u2013 Model View u2013 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.
My question is that : Do i know need to create three model views for these three message types?? Are these steps sufficient?
Please let me know if some other things needs to be followed or U know more simpler way to RFC connect so that I can pull data from ECC into BI and practice delta management.
Thanks
Edited by: max.sap on Apr 28, 2011 8:24 AM

Hi Niru,
Have you created a
[RFC destination in NW Administrator?|http://help.sap.com/saphelp_nwce10/helpdata/en/5a/97a066223e440b8ead3da027b17d9e/frameset.htm]. Have you created a [BI System connection?|http://help.sap.com/saphelp_nwce10/helpdata/en/7e/6dbcea3700452195e3bddaa47c5906/frameset.htm]
Best regards,
Dharmi

Similar Messages

  • RFC connection problem in ECC 4.7 and ECC 6.0

    Hello friends,
    Created RFC connection in 4.7 version of SAP and used it in a java program.  (STFC_connection) was the function module used.
    it all worked fine. Later when i tried the same thing in ECC 6.0 it failed and throws communication_failure exception .
    please guide me in this issue.

    Hi...
    Check the Unicode/Non unicode status in MDMP&UNICODE  tab present in transaction SM59 while chking the connection.
    if your ECC6.0 is unicode system then you need to check the radio button present for Unicode in  MDMP&UNICODE   tab.
    Regards,
    Lokeswari.

  • Connecting Jco and ECC

    Hi Gurus,
           I just changed the ECC client 100 to 200 in Jco connections but Portal is not communicating with backend ECC clent 200. Please advice.
    Regards
    Francis.

    Hi,
          Changing the Joc connection is not working. Therefore I created a Jco connection again. It's working fine. I'm closing this forum.
    Thanks
    Francis

  • Data load from R3 is slow and gives rfc connection error

    Hi all, is there any debug capabilties available on BI 7.0 when it comes to debug data load from R3 using rfc connection ( aleremote and bwiremote users )
    any ideas where can I look for solution.
    thanks.

    Hi,
    Check the connection between the R/3 and BW.
    or It may be the network problem contact system admin or basis people.
    thanks,
    dru

  • Is it possible to have BW3.5 NON UC and ECC UC

    We have to perform Unicode conversion as we have ECC5.0 NON UC and BW3.5 also NON UC(the final picture is of course ECC 6.0 and BI 7.0 or some latest).
    Here I wander (as this are quite huge systems how to perform this.(I am afraid we will not be able to perform unicode conversion for productive ECC and BW at the same time).
    With lack of experience I would kindly ask you is it possible to have BW3.5 NON UC and ECC UC(or oposite if necessary). I assume it is only metter of RFC connection (UC and NON UC but need approval)
    Thank you a lot in advance

    it is

  • Unable to create RFC connections

    I got a message to update a managed system. I start managed system configuration and select the affected system, configure system step 3 connect managed system. At this point I get an error stating "Error when opening and RFC connection (lb: Hostname or service of the message server unknown"  I have tried pinging the system by hostname from the solution manager server and it pings fine. I ran a connection test from the Solution Manager server to the managed system using the one RFC connection available and it connects well also. When I look in the work directory there is an error message repeating the above. Not sure what else I can look at there, I entered the system into the HOSTS file on the solution manager server to see if it made a difference it doesn't. Attached is the entry in the DEV_RFC log from the work directory it won't paste into the question for some reason
    Thanks In Advance
    Troy
    Specifics
    Solution Manager 7.1 SP6
    Oracle 11.2.0.4
    Windows 2008 R2

    Hi Troy,
    I got a message to update a managed system. I start managed system configuration and select the affected system,
    For the affected system i would like to check the SAPOSS connection on the specific system first with OSS1 tranx.Here i suppose on testing SAPOSS connection on the affected system you'll get the error
    (lb: Hostname or service of the message server unknown)
    Kindly share the OSS1 configurations screenshot( If possible) at affected system and confirm the SAPOSS connectivity on same system.
    Regards,
    Gaurav

  • How to config.  rfc connection

    hi all,
    how do we config. RFC connection,JCo and SLD plz give me good example also..
    Regards

    Hi..
    A good example for RFC:
    http://help.sap.com/saphelp_nw04/helpdata/en/41/38bc8f813719488ddc9d9b21251ec3/frameset.htm
    SLD Configuration Doc:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a0d7c290-0201-0010-bbaa-d8f8af341796
    Jco:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
    For Web Dynpro Backend Access( It contains Everything) :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/webcontent/uuid/5b77db42-0a01-0010-d7ba-8aa375593dd3 [original link is broken]
    Do reward points if helpful!
    Regards
    Puneet

  • Cofig guide for connecting CRM and R3 system

    Can anyone provide full cofiguration guide for connecting CRM and R3 system from end to end.
    also complete information about bdocs settings in Adminstration console.
    regards,
    Sunil

    Hi
    Please follow the link
    http://help.sap.com/saap/sap_bp/CRM_701_XX/Html/index.htm
    then go to the following hyperlinks
    B01: CRM Generation
    B09: CRM Customizing Replication
    C03: CRM Master Data Replication
    Meticulous follow these three documents then you will be able to connect CRM AND ECC systems and will be able to perdorm initial load of customers, materials etc
    please let me know if you have any issues
    thanks
    Ananda kumar karri

  • RFC connection error between BW 3.5 and ECC 6.0

    Hi gurus,
    We've defined an RFC destination between BW 3.5 and ECC 6.0. Connection test  (SM59) is ok, but authorization one fails and ALEREMOTE users block. These users on both systems have good profiles. We look ST22 and find a runtime error on CALL_FUNCTION_REMOTE_ERROR. We've cleaned source system on BW and RFC destination and we've created one more time, but error doesn't disappear. We've looked OSS but don't find anything.
    Any idea? Is there any other place (users, RFC) where we have to change user password on system?
    Thanks a lot!
    Regards,
    Iván.
    Edited by: Iván Cabezas Castillo on Nov 6, 2009 12:09 PM

    Solved!
    This is because of the incompatibility of password handling between
    640 and 700 systems.
    We have to use a maximum 8 character long password with only capital letters (numbers are also allowed) for the user "ALEREMOTE".
    1. Change the password for the user in SAP R/3.
    2. Maintain the password in SAP BW for the RFC destination (transaction SM59 - Logon/Security tab)
    3. Authorization test is now successful.
    (SM59 - Test - Authorization).
    Regards!

  • Create RFC connection in RSA1 for BW from client 302 to ECC 101 and 151

    Hi Friends,
    I have to create rfc connection in BI.
    I have one client in BI ie302 and two cliwnt in Dev ie101 and 151.
    Now I have one connection which is working fine ie 302 to 101.
    NO my requirment is to create another connecitons ie 302 to 151.
    Kindly sugest if it is feasible and is there any specific settings for the same.
    I tried but at a time only one connection is working fine.
    Thanls in advance.
    regards
    Jiggi

    Hi,
    Can you check  if there is any other user ID specified in "BW user for ALE".
    To check, Go to transaction RSA1 --> Settings --> Global Settings.
    If you find a different user id there, then specify the correct BW user id there.
    Please refer to OSS Note 410952 for details.
    Hope this solves your problem!!
    Regards,
    Raj.
    Edited by: Raj on Aug 14, 2009 8:15 PM
    Edited by: Raj on Aug 14, 2009 8:16 PM

  • RFC connection error for PS_ACCESS_1 and PS_ACCESS_2

    dear all,
    i have created the RFC destination PS_ACCESS_1 and PS_ACCESS_2 with TCP/IP. i also installed WDPS* files in *sapgui\ps\access folder. now i m checking for 'TEST CONNECTION' in sm59 for PS_ACCESS_1 and PS_ACCESS_2 but it is giving  'Error when opening an RFC connection' this error. pls suggest the solution for this problem.
    am i missing any other settings? i m using SAP ECC 6.0. is it comfortable with this? is it required any configuration from basis side?
    regards,
    vicky.

    HI,
    please check the RFC Trace File at SM59 -> RFC -> Show trace file.
    For better tracing delete the Trace File first and recheck the RFC Dest.
    Regards,
    Gordon

  • RFC connection from SAP Data services to SAP ECC

    We have data services set up in linux machine. I am trying to set up RFC connection between data services and SAP ECC.
    From data management console after creating RFC connection i am getting "RFC_bad_connection" error message. Username , password, system number, hostname and client is working from SAP GUI and has all the authorizations. SAP  gateway and service is name is correct.
    Did anyone had similar issue and what was the solution. Do we have start the RFC connection from linux data services machine, i didn't see any sh executable to do so.
    Thanks in advance for helping to solve the RFC connection issue.
    Edited by: gupta sasha az on Dec 19, 2011 7:24 PM

    I am new to SAP and we have just started work on Data Services.
    I wanted to know the complete procedure as in how can I establish a connection between Data Services and ECC.
    Thanks for your help and time.

  • Connectivity between SAP ECC system and SAP BI

    Connectivity between SAP ECC system and SAP BI
    Hi BI-experts!
    I would like to load e.g. transaction data from SAP ECC system into SAP BI system.
    The Loading process is hanging in processing step u201CSERVICE APIu201D.
    The process  in hanging in status "yellow" and then changed after a while to status u201Credu201D.
    [0FI_AR_4 |http://www.file-upload.net/view-1447743/0FI_AR_4.jpg.html ]
    The following steps within Load process are yellow and then red:
    Extraction (messages): Missing messages
    Missing message: Request received
    Missing message: Number of sent records
    Missing message: Selection completed
    Transfer (IDocs and TRFC): Missing messages or warnings
    Request IDoc : Application document posted (is green)
    Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished
    Info IDoc 1 : sent, not arrived ; Data passed to port OK
    Info IDoc 2 : sent, not arrived ; Data passed to port OK
    Info IDoc 3 : sent, not arrived ; Data passed to port OK
    Info IDoc 4 : sent, not arrived ; Data passed to port OK
    Subseq. processing (messages) : Missing messages
    Missing message: Subseq. processing completed
    DataStore Activation (Change Log) : not yet activated
    Question:
    Can some one tell me whether my distribution model or other settings are wrong?
    I created 2 distribution model (BD64), one from SAP BW system and other from SAP BI system with message types RSRQST, RSINFO, RSSEND
    Thank you very much!

    Hi Holger.
    this issue is related to the RFC but not the one which is communicating from BI to R/3 rather the one which is communicating from R/3 to BI follow these steps.
    1. check your BI system logical name from the myself source system.
    2. go the ECC and run the transaction sm59
    3. go the ABAP Connection folder and search for your RFC which name would be by default as per your BI logical system name.
    4. double click it and edit it now check whether the Target hostname or ip is OK.
    5. In the logon tab check the client number User and password settings.
    Save it and test it with both Connection Test and Remote Logon.
    if every thing work fine i hope your problem will be solved.
    kind regards,
    Zeeshan

  • Any SAP Note for RFC Error between BI and ECC 5.0

    Hi..
    the RFC Destination between BI and ECC 5.0 is giving errors.
    Plz let me know if there is any Support pack  or any solution to fix this error.
    thanks..

    Hi,
    pls find the RFC connection details
    1 Prerequisites
    1.1 User Roles
    Use
    With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
    Technical name Description File name for upload
    B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
    B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
    C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
    B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
    Procedure
    Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
    2 Local Settings
    This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
    2.1 SAP R/3
    2.1.1 Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu Define Client Administration (SAP R/3)
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    Then carry out the following steps:
    1. Choose Display  Change.
    2. Confirm the warning message Caution: The table is cross client.
    3. Select your SAP R/3 client and choose Details.
    4. In the Change View Clients: Details screen, activate the following settings:
    u2022 Automatic recording of changes
    u2022 Changes to Repository and cross-client Customizing allowed
    u2022 eCATT and CATT allowed.
    5. Save.
    6. Go back to the SAP Easy Access menu.
    2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1. Define the systems as logical systems.
    2. Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code SPRO
    SAP R/3
    IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
    2. Choose New entries.
    3. In the column Log System, enter a name for the logical system that you want to create.
    4. In the column Name, enter a description of the logical system.
    Log. System Name
    where XXX is the system name
    and NNN is the client.
    5. Save your entries.
    A transport request for Workbench appears.
    6. Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7. Select an existing request or create a new request, if necessary.
    2.1.3 Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Assign Logical System to Client
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Choose Display ® Change.
    3. Confirm the warning message The table is cross client.
    4. Select your R/3 client and choose Details.
    5. Enter the name of the logical system of your SAP R/3 client.
    6. Save and confirm the warning message Be careful when changing the logical system.
    7. Choose Back twice.
    2.1.4 Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Creating an RFC User (SAP R/3)
    Transaction Code SU01
    SAP R/3 Menu Tools  Administration  User Maintenance  Users
    2. In the User field, enter RFCUSER.
    3. Choose Create.
    4. On the Maintain User screen, enter the following data on the Tab entry screens:
    Address
    Last Name
    Function
    Logon data
    User type System
    Password LOGIN
    Profile
    Profiles SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language EN
    5. Save your entries.
    2.3 SAP BW
    2.3.1 Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1. To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu Local Settings ® Define Client Administration
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Switch to change mode.
    3. Select your client.
    4. Choose details.
    5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6. In field Client Role enter Customizing
    7. Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2 Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
    Transaction Code SPRO
    IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
    1. A dialog box informs you that the table is cross-client. Choose Continue.
    2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
    3. On the New Entries: Overview of Added Entries screen enter the following data:
    Field name Description R/O/C User action and values Note
    Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
    Name Textual Description of the Logical System Enter a clear description for the logical BW system
    4. Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3 Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu Assigning Logical System to Client (SAP BW)
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    1. In the view Display View "Clients": Overview, choose Display.  Change
    2. Confirm the message.
    3. Select your BW client.
    4. Choose Details.
    5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6. Save the entries and go back.
    2.3.4 Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Modeling  Administrator Workbench: Modeling
    Transaction Code RSA1
    1. In the Replicate Metadata dialog box, choose Only Activate.
    2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5 Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Creating RFC User
    Transaction Code SU01
    SAP BW Menu Tools  Administration  User Maintenance  Users
    Then carry out the following steps:
    1. On the User Maintenance: Initial Screen screen:
    a. Enter the following data:
    Field Entry
    User RFCUSER
    b. Choose Create.
    2. On the Maintain User screen:
    a. Choose the Address tab.
    b. Enter the following data:
    Field Entry
    Last Name RFCUSER
    Function Default-User for RFC connection
    c. Choose the Logon data tab.
    d. Enter the following data:
    Field Entry
    Password LOGIN
    User type System
    e. Choose the Profiles tab.
    f. Enter the following data:
    Field Entry
    Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g. Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6 Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu Define RFC-USER as default (SAP BW)
    Transaction Code RSA1
    SAP BW Menu Modeling  Administrator Workbench: Modeling
    1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
    2. In the Global Settings/Customizing dialog box choose Glob. Settings.
    3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
    a. Choose Display  Change.
    b. Enter RFCUSER in the BW User ALE field.
    c. Choose Save.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • XI Dev. connected to ECC Dev and ECC Qas

    Hello Folks,
    I have a question -
    We have 2 XI systems: Development, and Production (no QAS)
    And 3 ECC systems: Dev, Qas and Prd.
    Now we have the XI Dev connected to the ECC Dev.
    I'd like to know if it's possible to also connect the XI Dev System to the ECC Qas system.
    I mean, to create the RFC dest. in both systems, a new Business System for ECC QAS; and all the necessary config.... and if it won't take problems when we have to transport the Interfaces from DEV to PRD.
    Thanx in advance.
      Juan

    Hi juan,
    just be carefull when you add you QUA config in ID and then when you will transport...
    1. in your ID, when will define the config with QUA, do NOT ADD the object to your Scenario.... if for the transport you choose the option "Transport all objects of my Scenario"... else you will have a problem in Prod because of the system QUA. Indeed with transport DEV become PROD but your ECC QUA cannot become ...
    2. when you will transport to your PI prod :
       - check my first point or use option "Transport by selecting each objects" and choose only object linked link to your DEV.
       - delete also the Condition option (if you have one) in the Receiver Determination if in th receivers list you have DEV and QUA.... because after the transport the ECC QUA become nothing.
    So yes we can. There is no technical issue.... if you do properly the things !!
    Regards.
    Mickael

Maybe you are looking for