RFC CONNECTION CHECK

Re-Connect R/3 and BW

Introduction This document describes how to re-connect BW (v3.0B) to your R/3 source system. Normally the connection will have been ‘lost’ when a test system has been refreshed from a production system. This procedure needs to be done on the ALL systems, (BW, R/3 ,CRM, SEM etc) and for each layer (Production, QA, Development). Find out if your connection is working in the first place by going into the Admin Workbench; Source Systems. Right Click your source system and select “Check”.

Type Transaction WE30. Check iDoc types

a.)  Enter 'RSSEND' in the Obj. Name field.  You will see an entry similar to the one below:

RSSEND                          Data transfer from the source system (template)

[-]  E1RSSH               Data transfer IDoc: Header information

[+]  E1RSHIE    Data transfer Idoc: Hierarchy header information

E1RSTXT   Data transfer IDoc: Texts

b.)  Enter RSREQUST in the Obj. Name field.  You will see an entry similar to the one below:

RSREQUST                    Data request to the source system

[-]  E1RSRH               Data request IDoc: Headersegment

[+]  E1RSRHI     Data request IDoc: Hierarchy

[+]  E1RSRTX    Data request IDoc: Texts

[+]  E1RSRMD   Data request IDoc: Master data

[+]  E1RSRIS      Data request IDoc: InfoSource

c.)  Enter RSINFO in the Obj. Name field.  You will see an entry similar to the one below:

RSINFO                         Info IDoc

[-]  E1RSHIN             InfoIDoc: Status segment

E1RSPIN            InfoIDoc: Data packet segment

E1RSEIN            InfoIDoc: Error segment

d.)  If any of the above do not exist, contact your BASIS Team.

Type Transaction SM59. Maintain RFC destinations

a.) Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding yoursource system d.) Logon Information should contain source system client and name & password for you remote logon. We use RFC_SAB for BW logon to R/3 and RFC_AAE for R/3 logon to BW. Password for both is always xxxxxxx. e.) Execute your 'Test Connection' & 'Remote Logon'. You should NOT be prompted for a password, if you are then the logon info is incorrect. f.) Repeat above to verify RFCs for other systems (CRM etc)

Type Transaction WE21. iDoc Processing Ports.

a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 version.(BW 2.1C should be release 4.x) d.) RFC Destination should be one created in SM59. If non-existent then create one

Type Transaction SE16. Data browser (for R/3 ßà BW Connections)

Enter RSBASIDOC Print out copy of all entries in table. You should have one entry for each source system(SAP R/3, Flat File, CRM, etc The critical fields are : Source system - Name of Source from RFC DWH System - Name of Data Warehouse (BW Client Name) Object Status - Should be 'INA' until you replicate then status will change to 'ACT' Basic type - Must match setting in EDIMSG table TranStructure Prefix - see below: Source Systems Transfer Structure Prefix Flat File AA Business Warehouse AB SAP R/3 BA CRM BB Source System - see below: 3 - SAP R/3 from version 3.0D onwards B - External system, data and meta data trns. with staging BAPIs F - External system, meta data manually, data with file interf. M - Myself , Data Marts

Type Transaction SM30. Msg Types & Assignment to iDocs

Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOCtable for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missingentries.

Go to the SM30 main screen. Clients Overview

Enter 'T000' in the Table/View field. Click 'Maintain'. Verify correct Client and Description. If incorrect enter.

Summary

This concludes our preparatory work. We have created all the necessary pieces to create our Partner Profile. To review: Verified existence of all message types. We have an RFC for all of our Source Systems. We have a Port setting for our Transactional RFC All source systems are assigned with entries in the RSBASIDOC table. We have our RSSEND / Idoc Type (ZSBAXXX) entry exists in the EDIMSG table We have ensured our BW client is set up.

On BW Type Transaction WE20. Partner Profiles

Click on 'Partner Profile' and then 'Partner Type LS' . Click on your Source system profile to verify settings. If Source System does not exist; Click on 'Partner Type LS' then Create. In your Outbound, Parameter should be 'RSRQST' . Double click it. Outbound Options Tab Receiver Port : select RFC from above step #3. Packet Size: 1. Output Mode: 'Transfer IDocs Immediately. IDoc Type : RSRQST. Syntax Check : 'X' Post Processing Tab Type : 'US' User : Remote User (RFC_R3) Language : EN

In your Inbound Parameters should be 'RSINFO'. Double click. Inbound Options Tab Process Code : 'RSIN'. Syntax Check : 'X' Process By Function Module: 'Trigger Immediately > Post Processing Tab Type : 'US' User : Remote User (RFC_R3) Language : EN

In your Inbound Parameters should be 'RSSEND'. Double click. Inbound Options Tab Process Code : 'RSDR'. Syntax Check : 'X' Process By Function Module: 'Trigger Immediately Post Processing Tab Type : 'US' User : Remote User (RFC_R3) Language : EN

On R/3 Type Transaction WE20. Partner Profiles

Click on 'Partner Profile' and then 'Partner Type LS' . Click on your Source system profile to verify settings. If Source System does not exist:

Click on 'Partner Type LS' then Create. d.)  In your Outbound Parameters should be 'RSINFO'.  Double click.

Outbound Options Tab Receiver Port : select RFC from above step #3. Packet Size: 1. Output Mode: 'Transfer IDocs Immediately. IDoc Type : RSINFO. Syntax Check : 'X' Post Processing Tab Type : 'US' User : Remote User (RFC_BW) Language : EN In your Outbound Parameters should be 'RSSEND'. Doubleclick. Outbound Options Tab Receiver Port : select RFC from above step #3. Same asRSINFO. Packet Size: 1. Output Mode: 'Transfer IDocs Immediately. IDoc Type : Basic IDoc Type (ZSBAXXX) that was checked or created in Step #5. Syntax Check : 'X

Post Processing Tab Type : 'US' User : Remote User (RFC_BW) Language : EN In your Inbound Parameter should be 'RSRQST' . Double click. Inbound Options Tab Process Code : 'RSRQ'. Syntax Check : 'X' Process By Function Module: 'Trigger Immediately Post Processing Tab Type : 'US' User : Remote User (RFC_BW) Language : EN

Check all is correct

To check that everything is now set up correctly, start back at the Partner Profiles main screen. a.) Find your source system b.) Double click on RSRQST from Outbound Parameters. c.) Double click on receiver port. Should bring you into PortSettings / RFC. d.) Double click on Port (Right side of split screen). This should bring you into the RFC Destination. e.) Execute your 'Test Connection' & 'Remote Logon'. You should NOT be prompted for a password. If you are then your logon info is incorrect. If not then all is well and this concludes your set up in Business Warehouse.

Troubleshooting

Still no joy? Try disconnecting and reconnecting the comms as below. On R/3 Disconnect R/3-BW Comms Type Transaction SE16. Enter RSBASIDOC a.) Print out copy of all entries in table. The critical fields are : Source system - Name of Source from RFC DWH System - Name of Data Warehouse (BW Client Name) Object Status - Should be 'INA' until you replicate then status will change to 'ACT' Basic type - Must match setting in EDIMSG table TranStructure Prefix - see below:

Source Systems Transfer Structure Prefix Flat File AA Business Warehouse AB SAP R/3 BA CRM BB > Source System - see below: 3 - SAP R/3 from version 3.0D onwards B - External system, data and meta data trns. with staging BAPIs F - External system, meta data manually, data with file interf. M - Myself , Data Marts > b.) You should have one entry for each source system(SAP R/3, Flat File, CRM, etc)

Type Transaction SE37. a.) Execute RSAP_BIW_DISCONNECT_40 using Single Test . b.) Use the following parameters matching information from Step #1. I_BIW_LOGSYS = BW system (RLOGSYS from RSBASIDOC (e.g. PAB050) I_OLTP_LOGSYS = OLTP Source system (SLOGSYS from RSBASIDOC) (e.g. AAE050) I_FORCE_DELETE = 'X'. c.) Repeat this for all entries in table RSBASIDOC

On R/3 Reconnect R/3-BW Cmms Type Transaction SE37. a.) Execute RSAP_BIW_CONNECT_40 using Single Test . b.) Use the following parameters matching information from Step #1. I_LANGU Language of the destination to BW I_SLOGSYS OLTP Source system (SLOGSYS from RSBASIDOC in BW) AAE050 I_LOGSYS BW system (RLOGSYS from RSBASIDOCin BW) SAB050 I_STEXT 20 times second byte of TSPREFIX from RSBASIDOC in BW (Example TSPREFIX = 'BA', then I_PREFIXE = 'AAAAAAAAAAAAAAAAAAAA') I_BASIC_IDOC BIDOCTYP of RSBASIDOC in BW I_TSPREFIX TSPREFIX of RSBASIDOC in BW I_SAPRL SAPREL of RSBASIDOC in BW I_RESTORE

Examples of problems

Reference to BW does not exist on R/3 system. Solution is to add an RFC entry in transaction SM59. This also needs to have an entry for a profile to log on to the BW system for the “Test Connection” option in BW to work. Without the above entry, the RSAP_BIW_CONNECT_40 program to add the entry to the RSBASIDOC table will not work. Sap R/3 needs to be in modifiable status for this to work. Once AAE has been restored all the Partner Profile User Id’s on (WE20) on the BW side default to SAP*. These need to be reset to RFC_AAE. Need to Activate the AAE Source system from BW before trying Check option RFC_SAB user profile non-existent on AAE. Need to recreate it.

Transactions you need access to:

SM30 - Maintain Table Views WE30 - Develop IDoc Types SM59 - Display and Maintain RFC destination WE21 - Port Settings WE20 -Partner Profiles

Tables to maintain:

RSBASIDOC - Assignment of Source Systems to BW T000 - Clients EDIMSG - Message Types and Assignment to IDoc Types

Functions :

RSAP_BIW_CONNECT_40 (new version of function from notes 93821 & 184322) RSAP_BIW_DISCONNECT_40 (new version of function from notes 93821 & 184322)