RFC Configuration

Hi Guys,
Can you tell me about RFC Configuration in XI System?
cheers,
Charul

Hi,
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD u2013 System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
ALE configuration for pushing idocs from SAP to XI
Regards
Raja Sekhar

Similar Messages

  • XI 3.0 E-Filing GB R/3 RFC configuration to XI

    Hi
    Please could anyone advise me on the following. I am currently in the process of implementing E-Filing GB in XI 3.0 and I am stuck on what the RFC configuration should be in the R/3 Business System for the XI 3.0 configuration of E-Filing . I have referred to the blog [/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies |/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies ] and I want to confirm whether the PI 7.1 RFC configuration in the R/3 system would be the same for XI 3.0 as there is no clear SAP documentation about this. We had previously been using Business Connector for E-Filing.
    Many Thanks
    Rosie

    Yes in PI 7.1 also the same is applicable.
    As mentioned in blog -
    Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection in R/3.
    Same all settings u do.

  • Any step by step RFC Configuration guide available.

    Hi All,
              Any step by step RFC Configuration guide or Blog available to connect RFC function module with the NWDS.
    Thanx for Ur time.
    Cheers,
    Sam

    Hi,
    Once gone thru all those documents u need to folloe these steps.
    U need to configure  the SLD and techinical system if it is properly conneted then your work is easy.
    Then you have to go and crete the create the JCo Destination systems.
    After you can urilize the created JCO in your application.
    When you create the create the model you need to give the model names and Jco names and give the r/3 system details and get your function module from the R/3 side before need to make your fnmodule as Remote enabled and give the authrization roles.
    Then you can get  the Ur fn module into webdynpro.
    Thanks,
    Lohi.
    Thanks,
    Lohi.

  • PI 7.31 (single stack) posting to RFC configuration gives this error: om.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system extern ...

    Getting cryptic error while trying to post to a custom RFC from PI 7.31 single stack.
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system <extern>|pidevhost)
    Does anyone recognize this error and/or know of detailed instructions for registering custom RFCs in PI 7.31. I could possibly have configured the target wrong but no error says so.
    This is a File-->PI-->RFC scenario. The file processing is super simple and a configuration I have used successfully before. I would assume I'd get a different error if it couldn't parse the file.
    Jody

    Not shure if you already did but try getting some details with XPI Inspector. Also increasing log level for this category might help. You also may wanna check authorization (even if this should show with a different error text) in ECC using ST01.
    My guts feeling is that there is something wrong with payload / signature of RFC.
    Cheers
    Jens

  • GRMG RFC Configuration "HTTP method GET is not supported by this URL"

    Hi All,
    when i create the RFC Destinaton for SLD  with regards to GRMG Configuration and test the rfc i get the Reason code 400 with error "HTTP method GET is not supported by this URL".
    Even if i call  http://hostname:port/sld/rtc in the browser i get the same error.
    RFC Details:
    Target machine:Host
    Service No: port no
    path prefix: /sld/rtc
    My other RFC destinations for rwb,IR,ID,Adapter Engine works well.
    I would appreciate your suggestions on this
    Aravind

    Hi David,
    I feel sorry to wake this thread up after long time.
    It's the same situation, connection testing for SLD returns 400 "HTTP method GET is not supported by this URL".
    However, CCMS hearbeat seems to work fine with SLD. It returns green.
    I have a question here. Is it OK if we leave it that way without changing GRMG?
    Is there any potential problem, or side effect when the RFC destination returns 400?
    Thank you very much,
    Teyun

  • Is SAP-OSS RFC Configuration required for Technical Monitoring ?

    Hi Experts,
    I have not configured the SAP-OSS rfc connection.Is it required for setting up the technical monitoring(Tcode : SOLMAN_SETUP).
    If Yes can you please help me in solving the above problem.Our aim is to configure  technical monitoring for  system and self-monitoring.
    Thanks In Advance,
    Satheesh E

    Hello,
    I am assuming you are speaking about 100 concurrent users and not the entire company userbase.
    Core i5 (although is dual core underneath) is generally meant for desktops, having said this, please note that its difficult to arrive at any recommendation based on simply userbase. You need to have more data with you with respect to amount of transactions, concurrent users, peak period, load during peak period etc.
    You need to use SAP's quicksizer to calculate the amount of SAPS for your production servers, SAPS is the unit used to calibrate your hardware for running SAP Applications.
    If you provide your SAPS value to hardware vendor, they will advise what CPU rating and how many CPUs you need. They will infact tell you the entire configuration that you need.
    you can also buy the following book:
    http://www.sap-press.com/products/Sizing-SAP-Systems.html
    Regards,
    Siddhesh

  • RFC configuration for system monitoring / Early Watch reports

    Hello Basis Gurus:
    Please help me out.....
    The early watch reports in the solution manager of my system are failing consistently to execute.This is happening for all the 3 systems DEV,QAS,PRD.when i click on individual earlywatch reports it takes me to a screen which says  "data for this report is overdue.....go to your satellite system SDCCN to see why the data was not sent...."
    It says ...check the following things.....
    "The RFC connection for the SAP Solution Manager system is not working.
    The 'Task Processor' background job, which collects the session data, has been changed.
    Problems arose while data was being collected (see the detail log for the task that collects the session data).
    A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data."
    I can see the task processor job , and the periodic Maintenance package scheduled everyday and completed sucessfully.So is it the RFC which is causing the problem.
    Im SM59 of the solman, i can see system generated RFCs for the PRD,DEV,QAS and SND  (...3 for each of these systems...).
    say for PRD, these are the 3 RFCs.
    1.)SM_PRDCLNT<client#>_READ.
    2.)SM_PRDCLNT<client#>_TMW.
    3.)SM_PRDCLNT<client#>_TRUSTED.
    I am not sure which RFCs among the 3 for any given system does the solman use to communicate to the satellite systems.
    *The user id section in the Logon Data of any of these RFCs is blank.and the password says "is initial"...*is this correct.Does the user id have to be a communication type of user...
    PLeaase advise as to what could be going wrong..
    Regards.

    Hi,
    The system uses ABAP Connection (Connection Type 3) to connect to different Systems to execute Functional Calls.
    Now in your case, there are 3 different connections meaning your Basis Team has used 3 connections for different connection activities. This is totally a business dependent scenario.
    Now each time you create a RFC Connection, the system will need the following information to remotely call another system, they are:
    Host Details of Target System
    Logon Details to remotely login
    For RFC Connections the User Type has to be Communications User. But there are companies which use Dialog User Types as well to remotely login for some cases. When the User ID is created for an RFC User and a Password is assigned to it, this Password is considered as the Initial Password by the system. This Password is taken as the Initial Password in the RFC Connection as well.
    There can be cases where the system is Trusted and there is no need of a password, but an Username is mandatory in all cases. Remember if you set the system as Trusted, the password option gets deactivated and the connection wont work, if the system does not have the Trusted status.
    But in any case you must assign the Username alongwith the Client and Language Details in the RFC Connection for it to work.
    Hope this helps.
    /Manoj

  • BW and RFC problem  -- Source system not created.

    Hi Friends,
    Before posting this post , i have searched so many posts and docs and but still got a problem in creation of R3 source sytem in BI7.0.
    Steps i followed in R3 are as follws:
    1) created  alogical system for R3 and BI7.0
    2)assigned this logical system to clients 001 and 800
    001--Bi
    800--r3
    3)created user BWALEREMOTE in  su01  with profile sap_all
    Steps in BI7.0 are as follows:
    1) Created  logical systems  for Bi and r3
    2) assigned this logical systems to same clients
    3) created  user BWAleremote in su01  with profile SAp_ALL
    with respect to RFC's
    In R/3
    SM59--created a RFC name  same as logical system names
    for R3 RFC destination-- user is BWaleremote, client is 800
    for BI RFC destination -- user is Bwaleremote , client is 001
    when i checked the connections , i can sucessfully test the connections , But remote logins are having problems.
    r3 to BW is possible, but it is prompting the  password for BI again
    BW  to R3 is not possible.
    To my knowledge and search in forums,RFC connections are succesful, then it should not prompt for any passwords..so iam  wrong
    I also went into RSA!-- global settings-- i gave user as BWaleremote..
    Plz help me in this
    PAVAN

    Hi Pavan,
       The RFC configuration is probably wrong. Check the username/pswd that you are using to connect to the other system. Try logging normally through the sap logon pad using that username/pswd that you have mentioned in the logon tab in RFC connection entry. See if you are able to logon. In the remote logon, it should not ask for any password.
       If this succeeds, then create the source system in RSA1 in the BI box.

  • User password problem in RFC after system copy

    HEllo,
    we have a problem in ECC6.0 after system copy (refresh QUAL system by PRD data).
    BEfore doing this copy, we export RFC data (SM59 tables) of our QUAL system and after the refresh we reimport these RFC in our QUAL system. We don't want RFC comming from productive system.
    After this reimport, RFC configuration is ok but we have a problem with RFCuser password. In the password box we have "inconsistent"...
    Have you an idea to reimport succesfully these informations ?
    Thanks
    lionel

    Hello,
    We performed another refresh yesterday. But unfortunatly it was not working. Password are still inconsistent.
    This are exactly way we perform it:
    Before restoring DB :
    export table via R3trans for tables:
    RFCDES, RFCDOC, RFCATTRIB, RFCCHECK, RFCDESSECU, RFCSYSACL, RFCTRUST, RFCCMC, RFCGO, SXRFC, IBSSI_RFCDEST, PARAMVALUE, RSECACTB where ident LIKE '___/RFC%'
    export users via scc8
    Restore DB, truncate upper rfc tables,  import rfc Tables
    Check SM59 => inconsistent
    Migrate Secstore => still inconsistent
    Import Users via transport generated by scc8
    run scc7 as post actions
    Tuncatate/re-import rfc tables
    Check SM59 => inconsistent
    Migrate Secstore => still inconsistent
    What else could be done ?
    We have a lot of RFC. so re-enter all password is really a hudge task ..
    Thanks a lot for help

  • RFC Adapter  RFC to File

    Hi,
    Can somebody help me to view this thread. I am learning XI using RFC to File and I have got some difficulties in undestanding the Adapter Configuration.
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step from Michal.
    When I select this thread, I get blank page.
    Thanks

    Hello MK and Shabarish,
    I need a little more help from you.
    Here is XI Scenario.
    Want to send Material info using RFM from system A to System B via XI.
    Process: In System A, I create an RFM and send the data via dest paramter.
    It looks like this.
      Call Function
         dest 'SYSTEMA_SENDER'
    1. I created T - RFC Destination in systemA.
        RFC Name     SYSTEMA_SENDER
        gateway host  gbdsc1  ( using smgw)
        serveric          sapgw11
        Program id     SystemA_Sender
                             Registered server program, unicode.
    2. In XI box, in Integration configuration, Created RFC sender channel with the following paramter
        Adapter Type   RFC  - Sender
        RFC Server Parameter  -  
                 Applcation server(Gateway)  gbdsc1    ( As in RFC dest System A )
                 App service(gateway)           sapgw11
                 Program ID                          SystemA_Sender
        RFC Metadata repository     
                Application Servr         ( What do I enter here  is it System A)
                System Number
                Logon on User
                Logon pw
                Client
                 Language
      Finally,
    In system A when I do connection test I get the following errors
    Error: Program SystemA_Sender not registered
    Location SAP-Gateway  on gbdsc1/sapgw11
    Detail:TP SystemA_Sender not registered
    and other errors
    Can you identify any correction required for the above RFC destination and RFC configuration?
    Do I need to register the program and if so how?
    Your help is deeply appreciated.
    Regards

  • RFC sender adapter not running

    Hi there,
    I have following scenario: R3 -(rfc)-> XI -(ftp)-> LEGACY.
    In R3, i created a RFC DESTINATION (type T) : with Program_ID & GW options (hostname= R3 hostname & service= sapgwXX where XX means sys number). This RFC currently works!!
    In the RFC sender adapter, i used the same program ID and the same hostname and service mentioned above.
    If i execute SMGW + GoTo->Logged clients, i can see my program ID there but if i click on it, the register status is WAITING!!!!!
    Besides, if i execute the program, no information is transmitted to XI via RFC so i cannot see any error message.
    Do i have to do anything else??? Maybe i am missing something...
    Could you please help?
    best regards,
    david

    Hi,
    In sender RFC :
    Configuration takes place using a RFC adapter communication channel and TCode SM59 (Create rfc connections).
    - All systems that send an RFC via RFC Adapter require an RFC connection to the respective RFC Adapter(inbound). Metadata is gathered in the same way. Register the program id of the RFC adapter in SM59. The rfc destination must be of type "T" tcp/ip.
    - You cannot send IDocs using this rfc connection. you must send IDocs to the RFC destination of the IDOC Adapter.
    Also check out that Program id is case sensitive.
    in the functiion check out for the COMMIT WORK at the end of LUW.
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • RFC Source data not filled correctly

    Hi All,
    I am facing a typical problem.
    I have created a RFC to File scenario and I am running the ABAP program to call the RFC with the following values:
    field1(type Char 14; value:'aaaaaa')                   --> Field1 (string)
    filed2(type Char 15; value:'000000000000012')   -->Field2 (string)
    filed3(type Char 10; value: 'fgdf')                       -->Field3 (string)
    field4(type Char 8; value: 'sgsdfg')                    -->Field4 (string)
    However, the source structure in XI is getting filled with the following values:
    Field1 - 'aaaaaa'
    Field2 - '00000012fgdfsgsdfg'
    Field3 - Empty
    Field4 - Empty.
    This is in the source structure (before the mapping is done). I am unable to make out if the problem is there in ABAP program or in XI.
    I tried debugging ABAP program. But it looked perfectly fine. Is there something I need to change in XI for this scenario???
    Please reply its urgent.
    Reward points would be given.

    Hi
    First check if RFC is remotwe enabled.
    I hope u have created TCP/IP RFC connection in Sender System with program id and this same program id is maintained in the ID Sender RFC Configuration.
    Also check the program id should be same in both area --> Since it is case senstive.
    Also --> import RFC in IR , if u have made changes in RFC re import that's better.
    hope above is helpful
    rwd points if useful
    rgds
    srini

  • Retrieve data from R3 to XI using RFC

    Hi,
    I want to get data out from R3 to XI through RFCs or even using idocs. I have done RFC configurations in abap using SM59 with XI as destination. I am not sure whether its right. Please guide me as to how to get data out of R3 by first sending the ID no. to R3 and then retrieving data. Can anybody help me or give me some links where i could get some information about such a scenario?
    Thank you

    Hi Kevin,
    You need not to do any seeting at R3 side for RFC Scenarios.
    For RFC Scenario:
    Make RFC in R3 make sure that it is working fine in R3. take ID as a import parameter.
    Import the RFC Structure in XI in Imported Objects.
    Do the Design & Configuration as you do generaly.
    For IDOC Scenarios :
    Yuo have to do some setting in R3 and XI side . For Required setting refer following Links.
    Trouble shooting ALE settings.
    Troubleshooting of ALE Process
    Configuration steps for Idoc.
    Configuration steps required for posting idoc's(XI)
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    Reward Points if Helpful
    Thanks
    Sunil Singh

  • RFC to RFC testing!!

    Hi,
    How to test the RFC to RFC scenario?
    Also the necessary configurations settings on the sender adapter side?
    Is RFC going to support async mode.
    Please guide me in this issue.
    Thanks in Advance,
    Kiran

    For the sender RFC Configuration
    1. create a TCP/IP Connection in sm59 of the R/3 system.
    TCP/IP Destination Name
    Registered program id
    Port and IP address
    2. provide the same information in the sender CC of RFC.
    Receiver RFC Configuration
    1. Create a R/3 destination in sm59 of the R/3 system
    2 . Provide the same information in the Receiver CC.
    To test the RFC in Sync Mode
    1. go to SE37 and press F8
    2. Provide the TCp/IP connection in the destination and provide the parameters for the RFC.
    To test the RFC in ASync Mode
    call the RFC in background task mode .
    Syntax
    CALL FUNCTION func IN BACKGROUND TASK
                         [DESTINATION dest]
                         parameter_list
                         [AS SEPARATE UNIT].
    To analyse about the errors in the RFC
    http://www.saptechies.com/faq-xi-30-pi-70-pi-71-rfc-adapter/
    Thnz
    Mohamed

  • RFC sender adapter question

    Hi Experts,
    if we take RFC as sender adapter for communication. from PI aspect, the trigger mechanism is pull or push?
    in sender RFC configuration, we need to specify Application Server (Gateway), Application Server Service (Gateway), Program ID, Application Server, System Number and logon credentials. it is more like a pull mode, but i do not see any polling interval to be set, how does PI know when the data is ready?
    if the data is pushed from RFC sender system to PI, then there is no need to use a sender RFC channel as in SAP server the destination (PI) information of the RFC is already configured.
    Does someone can answer my query? Thanks in advance.
    Best Regards,

    Hi Aditya,
    in sender RFC configuration, we need to specify Application Server (Gateway), Application Server Service (Gateway), Program ID, Application Server, System Number and logon credentials. it is more like a pull mode, but i do not see any polling interval to be set, how does PI know when the data is ready?
    You would need to create a program that would trigger the Function Module and use the TCP/IP RFC destination you have configured in SM59.
    if the data is pushed from RFC sender system to PI, then there is no need to use a sender RFC channel as in SAP server the destination (PI) information of the RFC is already configured.
    The RFC adapter lies in the Java stack, that is why you would still need to configure the sender channel RFC in PI. Otherwise the connection will not work.
    Hope this helps,
    Mark

Maybe you are looking for