Program id in RFC sender

Hi Experts,
Please confirm if the same program id can be used in different RFC sender channels?
Thanks and Regards
Suma

Suma S wrote:
Please let me know what is the impact or result if I use the same program id in 2 rfc sender channel for 2 different scenarios
>
> Thanks and Regards
> Suma
Program ID of the registered server program. The selected program ID must uniquely describe the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters).
Quoting from sAP help docs
So, the impact of using the same program id wll lead to havoc
Regards
Krishna

Similar Messages

  • Program Id in RFC sender channel

    Hi Experts,
    Can the same Program ID be used in 2 different RFC sender channels? I do not want to use the existing RFC sender channel. Please le me know.
    Thanks
    Suma

    Hello.
    I can't understand what are you trying to implement here, but here is the correct way to work with RFC CC
    1. every sender CC should have the XI as the gateway server. the program ID is then registered on the xi server.
    2. If you want to call the same interface from different ECC systems, you will create an RFC destination in each of them, containing the XI as the gateway and the same program ID. in that case you fill the RFC Metadata Repository Parameter with one of the ECC systems (as the RFC have the same metadata in both servers - it doesn't matter which one is written there) look here for more information: [Configuring the Sender RFC Adapter |http://help.sap.com/saphelp_dimp50/helpdata/EN/67/6d0540ba5ee569e10000000a155106/frameset.htm]" and focus on the sentence: "The RFC metadata repository parameters identify the SAP system containing the repository for the RFC metadata. This does not necessarily have to be the sender system" (:
    3. If you want to use different interfaces - you will use 2 program IDs, 2 sender channels, 2 sender agreements.
    hope it helps.

  • Help with RFC sender, Program And RFC Destination

    Hi!!
    my scenary is asynchronous
         RFC Sender -> SAP-XI -> Oracle reciever
    I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI  receive the message but the message is empty.
    1. In my program on the line
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
    2. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
    3. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
    What is my Error?
    Where am i making a mistake?
    RFC
    FUNCTION zbapi_sd_ped_ord_servic.
    *"Interfase local
    *"  TABLES
    *"      PED_ORDEN STRUCTURE  ZSD_RFC_T04
    *"      RETURN STRUCTURE  ZSD_RFC_R06
      TABLES: zsd_ped_orden, zsd_rfc_r01.
      DATA: tb_ped_orden LIKE zsd_ped_orden  OCCURS 0 WITH HEADER LINE,
                     tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
    *Get Pedido by Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
              FROM zsd_ped_orden
              WHERE estatus  EQ  space.
      LOOP AT tb_ped_orden.
        MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
        APPEND ped_orden.
        tb_ped_orden-estatus = 'X'.
        tb_ped_orden-fecha_actualiz = sy-datum.
        tb_ped_orden-hora_actualiz = sy-uzeit.
        MODIFY tb_ped_orden.
      ENDLOOP. 
      MODIFY  zsd_ped_orden FROM TABLE tb_ped_orden.
      COMMIT WORK.
    *Errors in Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
              FROM zsd_rfc_r01
              WHERE estatus  EQ  space.
      LOOP AT tb_rfc_orden_error.
        MOVE-CORRESPONDING tb_rfc_orden_error TO return.
        APPEND  return.
        tb_rfc_orden_error-estatus = 'X'.
        tb_rfc_orden_error-fecha_actualiz = sy-datum.
        tb_rfc_orden_error-hora_actualiz = sy-uzeit.
        MODIFY tb_rfc_orden_error.
      ENDLOOP.
      MODIFY  zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
      COMMIT WORK.
    ENDFUNCTION.
    PROGRAM
    REPORT  ZBAPI_SD_PED_ORD_SERVIC.
    DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
          return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
         TABLES
              ped_orden             = ped_orden
              return                = return
      EXCEPTIONS
        communication_failure = 1
        system_failure        = 2
        OTHERS                = 3.
    IF sy-subrc <> 0.
      MESSAGE 'error' type 'I'.
    ENDIF.
    COMMIT WORK.
    RFC DESTINATION
    RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
    Connection TYpe: TCP/IP Connection
    Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
    Gateway host: host00
    Gateway service: sapgw00

    hi
    For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
    a) RFC destination
    b) RFC channel in the XI directory
    This weblog is a response to a few question about the basic configuration of the RFC sender adapter
    that were posted on the XI forum (and also on my e-mail)
    So here we go, basically we have to configure 2 things:
    a) RFC destination
    b) RFC channel in the XI directory
    RFC destination:
    1. To create the RFC go to TCODE: SM59
    2. Create new destination of type T (TCP/IP)
    3. Make sure you select Registered Server Program option before writing your program ID
    4. Write you program ID (remember it's case-sensitive)
    5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
    7. No configuration in the J2EE administrator nessecary
    Now we can proceed to RFC channel configuration:
    1. Enter your Application Server
    2. Your Application Server Service
    3. Enter your Program ID from the RFC destination
    And we're done:)
    Now you can test the RFC destination in SM59 to see if it works.
    Please chk this following link.
    1. RFC Processing with the RFC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
    2. Configuring the Sender RFC Adapter -
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
    3.  /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    regards
    Manas

  • RFC Sender Adapter configuration - Program ID question

    Hello All,
    I am working on a Sync RFC(R/3) --> XI --> Webservice scenario. I have a question on Program ID's. We're going to be having different RFC's call the same webservice. In that case, we'll have one scenario for each RFC sender.
    Do we need to create different TCP/IP ports and Program ID's in R/3 for each RFC sender or just one TCP/IP port and Program ID can be used by all RFC's from R/3?
    Please respond with your suggestions.
    Thanks in advance.
    Karthik

    Aamir,
    Buddy please correct me if i'm wrong!! As u said u will design this as single scenario with conditional receiver determination, Wht happen if I create RFC channel under some other Business Service with same Program ID. In this case my receiver is different isn't it!!!
    The key is Outbound Interface .. If the RFC sends BAPI_GET_DETAIL with say ProgramID TEST_1000 the corresponding interface in XI will be triggered, similarly if the RFC sends RFC_READ_TABLE with same program ID TEST_1000 the corresponding interface will be triggered?
    Is the above example make sense, please correct me if my understanding is wrong.
    raj.

  • Program not registered - RFC to J2EE (local machine)

    I have a local install of WAS on my laptop using MSSQL 2000. I am trying to integrate local portal into a BI system.
    1. I completed SLD configuration of local J2EE
    2. As part of local SLD config I specified a BW7 system as data supplier
    - entered  BW7 host & gateway
    - kept default settings for "configure data supplier targets" (i.e: sld/active=TRUE)
    3. In Visual composer I successfully triggered SLD data transfer
    4. In Visual Composer I specified a JCo RFC Provider to the BW7 system I want to access.
    5. If I go to BW7 and goto tcode SMGW -> GOTO -> Logged on client, I see 2 pair of entries for JCo RFC provider
    with the following settings
    - system type: Registered Server (REGISTER_TP)
    - state: connected
    - LU name & Host Name = J2EE Host name w/ last 4 characters truncated. Only first 8 characters appear.
    - TP Name: 2 entries = SLD_UC & 2 entries = SLD_NUC. So a total of 4 connections. My understanding is that TP Name is supposed to = Registered Server Program
    6. In BW7, I have an RFC w/ Registered Server Program setting and program ID = JCo RFC Provider program ID
    7. In BW7 RFC & JCo RFC the host & gateway settings are the same, they both refer to the BW7. THIS IS THE PART WHERE I AM UNSURE. I would have thought that the host & gateway settings of BW7 RFC would refer to Local J2EE engine. AND I DON'T KNOW WHAT THE GATEWAY IS FOR LOCAL J2EE.
    8. In BW7 when I try to test the RFC, I get errors:
    - Logon     Connection Error
    - program <...> not registered / CPIC-CALL: 'ThSAPOCMINIT' Tran
    - ERROR: program <...> not registered
    - DETAIL: TP <...> not registered
    - COMPONENT: SAP-Gateway
    - MODULE: gwr3cpic.c
    - RETURN CODE: 679
    - SUBRC: 0
    - RELEASE: 700
    - VERSION: 2
    9. I completed step 1 & 2 of RSPOR_SETUP
    - Step 1 <Create RFC Destination in J2EE engine> messages:
    No Authorization to SMGW
    Profile parameter login/create_sso2_ticket is not set to 2
    Check of RFC destination <...> with RFC_READ_TCPIP_DESTINATION successful
    - Step 2 <Create RFC destination to Portal> messages:
    No Connection
    Option Send SSO tickets not active (see documentation)
    RFC CALL RFC_PING, destination <...> failed with sy-subrc =2
    There a little something missing. Hope u gurus can help, lost a weekend over this.

    Hello,
    we get the same message (program ... not registered, COMPONENT: SAP-Gateway) in sm59, when checking the TCP/IP connection. We got it, after we changed the user name in the Visual Administrator.
    Does anyone know with which tool and where the program can be registered. (The connection has no user name (connection by SAP ticket)).
    Best regards,
    Thomas

  • R/3 to PI using RFC Sender Adaptor as Asynchronous scenario

    Hello Folks,
              RFC Adp.           SOAP Adp.
    ECC-->XI--
    >ARIBA
    I am new to PI and doing a scenario mention above. we are using RFC sender adaptor to send the data to XI in asynchronous process.
    I have config the Sender comm. channel as below.
    Appl.  Server(Gateway):  My Ecc Server host name
    Appl. Server Service (Gateway) : My Ecc server
    Program Id : XYZ.
    Note : while creating the the Service interface and Message mapping and Operation mapping I am using the RFCname.respone message type is that ok in asynchronous process?
    And then I went to ECC in Tcode SM59 and created a RFC destination of type TCP/IP
    and put the same information as given above and test the connection which is working fine.
    I have created a FM at ECC end make it remote enabled. and calling the FM in back ground task using destination in a Work flow code.
    When I run the Work flow code It ran successfully but i went to XI side there is no msg in the SXMB_MONI.
    Then i went to the component monitoring->Adatptor engine>Comm. channnel Monitoring and found that under my RFC sender comm. channel there is an error msg saying
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'BS_ECC', toParty '', toService '', interface 'YFPS_MM_I_0242_PO_APPROVAL_OUT', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_0242_PO_Approval_RFC_Sender' (channelId 19585252a58335ee871e4c3a771b027f)
    Where as i have checked that in the sxi_cache t-code there is a sender agreement for my scenario under the sender agreement tab.
    Please Help me in this to resolve the above error. I am totally stuck at this point.I would really appreciate a quick answer.

    Appl. Server Service (Gateway) : My Ecc server
    Confused with this statement.....
    it should have the format sapgwXX ....
    XX is the system number which comes from the j2ee port mentioned in the XI homepage URL
    http://<hostName>:5XX00:rep/start/index.jsp
    How to configure sender RFC adapter...check this blog:
    https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1438
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
    senderAgreement not found:
    Sender Agreement is Expected in this communication which does not seem to be present in ID....create sender agreement using the RFC communication channel....
    Regards,
    Abhishek.
    Edited by: abhishek salvi on May 2, 2009 1:24 AM

  • Rfc sender problem(sap r/3 -se37) 'alternativeServiceIdentifier: party/serv

    Rfc sender problem: While executing the rfc in sap r/3 system
    It is showing abap run time errors are
    'alternativeServiceIdentifier: party/service from channel
    configuration are not       
    (i have taken hint from this weblog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step)
    These are the configuration at sap xi and sap r/3 system
    1) SAP XI (ID)
    I have created rfc sender commuication channel in I.D.
          Rfc server Parameters->
                A.S.(Gateway)-> server    {sap r/3 server name}
                A.S.S.(Gateway) -> sapgw00 
                program id         -> PDPT
         AND RFC Metadata repository parameter
    2)SAP R/3 (SM59)
        Rfc destination ->  PPPP
        Connection type -> T
        Technical Settings->
             (*)  Registered Server Program
          Program ID  ->    PDPT
    Gate way options
          Gateway host -> server
          gateway service -> sapgw00
    Testconnection-> connected
    3) testing rfc at sap r/3(se37)
    But when i am executing a rfc in sap system
    Rfc target system -> PPPP
    and some import parameters
    and it is showing the error message as
    'alternativeServiceIdentifier: party/service from channel
    configuration are not  '
    4)SAP R/3( SMGW)
    CONNECTION TO CLIENT FOR PDPT(TP NAME) REGISTER STATUS IS WAITING
    Please help me how to solve this problem

    Hi,
    SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
    <i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
    A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
    - Give correct appserver and gateway service details in XI.
    - Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
    Regards,
    Prateek

  • RFC Sender Adapter - MP: exception caught

    Hi Friends,
    We have one RFC to SOAP scenario in our PRD system.
    When we execute an RFC in the R/3 side, the sender RFC CC receives the message. (The message id is generated). But, the message is not entered into SXMB_MONI.
    When we checked the audit log. The error is as below:
    RfcAdapter received sRFC for Z_RFC_SUPER_ACK from P88/300. Trying to send message synchronously.
    MP: entering1
    MP: processing local module localejbs/RfcAFBean
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection RFC_http://sap.com/xi/XI/System is currently not started.
    We have checked Program ID, RFC Connections in R/3 system. It is correct. The standard module "  localejbs/RfcAFBean -  Local Enterprise Bean " is used in the sender CC, only this module.
    We have few RFC receiver communication channels, all are working fine.
    Only this Sender RFC CC, we are facing this problem.
    We found the similar thread "RFC-Connection not started ?".  The same problem we are facing. They suggested to bounce the system and restart.
    Since it is PRD system, it is not able to do that immediately.  Since all RFC receivers are working fine, we feel that it is not required to bounce.
    Can you kindly help me friends, how to solve this problem.
    Thanking you,
    Kind regards,
    Jegathees P.

    Hi Sabarish
    The RFC sender cc is active in ID and started. 
    The status of the channel in CC monitoring is red. (due to this error).

  • RFC Sender (XI 3.0, SP14) Load Balancing doesn't work

    Hi all,
    We're "desperately" trying to use the Load Balancing option of RFC Sender Adapter (XI 3.0, SP14). It doesn't work.
    The Adapter can not register to the sender SAP server. But when we do not use the "Load Balancing" option, everything works well.
    We did follow the XI guidelines step-by-step. All necessary configurations in XI and in SAP sender system (TA: SM59) are "properly" done and reviewed by different experts several times.
    Do you have, by chance any running scenario using "Load Balancing" within a RFC Adapter? If yes, I would appreciate if you can share it with me. 
    Thanks a lot!
    Regards,
    Khaled

    Hello Khaled,
    the RFC sender adapter registers a program at the SAP Gateway. Load Balancing for the Sender Adapter means, that you have at least two J2EE server nodes within your XI installation. On all these server nodes the same RFC sender adapter is started and register the same program at the same gateway. The load balancing is then handled by the gateway. That means, that for the sender adapter the settings are the same, even if you use load balancing or not.
    The settings are, e.g.
    - SID=ABC
    - hostname=abchost (central instance, message server)
    - hostname=xyzhost (additional dialog instance of ABC)
    - instance nr=00
    application server (gateway): xi1host
    application server service (gw-service): sapgw00
    programm id: could be freely choosen
    The Metadata Repository could be connected using load balancing. Here a user need to log on to the system.
    The settings here must be:
    Message-Server: abchost
    Message-Server-Service: sapmsABC
    System-ID: ABC
    Logon-Group: e.g. PUBLIC; this logon group need to be created in system ABC using transaction SMLG
    For the RFC-Receiver Adapter the same settings as for the Metadata could be used.
    Keep in mind, that for the RFC Sender Adapter a RFC connection of type T must be created in transaction SM59 in system ABC.
    Rgds.,
    Andreas

  • RFC Sender problem  between 46D and RFC adapter

    Hi,
    I have this simple integration scenario where I want to send data to a archiving system;
    SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
    SAP side ***
    A Z-program using a Z func. like;
        CALL FUNCTION 'ZSD_DCF_SEND_TAG'
          IN BACKGROUND TASK
          DESTINATION 'XISYSTEM_TRFC_DCF'
          EXPORTING
            pt_filing_info = gt_filing.
        COMMIT WORK AND WAIT.
    XI side ***
    Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
    The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
    The problem in quality ***
    When sending just 1 msg, everything is just fine, message received and delivered to MQ.
    When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
    RFC_HISTORY
    - Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
    - OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
    My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
    It seems to me that the RFC adapter is kind of confused about the sender..
    I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
    - The SLD config. for bus.system Q93 is ok -
    - The bus.system in ID is showing correct vaues for
    Adapter Specific Identifiers (SID Q93, client 505)
    - Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
    - It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
    - It doesn't matter if I increase initial conn, max conn.
    I have also tried to use qRFC instead, but with the same result.
    Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
    Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
    Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
    best regards
    Torstein

    Hi,
    SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
    <i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
    A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
    - Give correct appserver and gateway service details in XI.
    - Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
    Regards,
    Prateek

  • Regarding RFC Sender Communication Channel

    Hi All,
      I am working on RFC sender channel, need some important information.
    1). Can i use single RFC Sender Channel in Multiple Sender Agreements.
    2). Can i use Program ID in Multiple Sender RFC Channels. I am having one RFC to File interface and another  RFC to JDBC interface.
         Do i need to create 2 sender channels and 2 RFC destinations with 2 Program Ids????.
    Please give me clarifications.
    Regards,
    Balu

    If i will use single sender RFC channel and Single Program ID for my all sender agreements, how that Single RFC channel
    will identify the information like
    In our sender agreement we configure not only the channel but also the Sender Interface (in your case RFC)......this is the factor which defines what to accept......in broader term we use the same concept of channel re-use in other cases also and the same work fine because of this Sender Interface.
    I found Q28 interesting: https://service.sap.com/sap/support/notes/730870
    In first read it may sound confusing...but after some more rreads you will know what the answer means in the SAP note.
    Regards,
    Abhishek.

  • Rfc Destination problem in RFC Sender Adapter

    Hi experts
    I created a Rfc destination type TCP/IP for Rfc Sender adapter.
    while creating i passed following parameter:
    1) I selected Activation Type option-> Registered Server  
    2)Given a Program id , same as i given in Rfc sender Adapter config.   
    3)Gateway option:
       i) Gateway Host:Server IP address where i created  Rfc.
      ii) Gateway Service:sapgw00
    After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

    Hi
    please check for the following things.
    1. check the RFC destination using the connection test tab in the R/3 system.
    2. check whether the program id that u have given is registered or not.
    to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
    check for ur program id name in the table.
    3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
    if u still face the problem please reply me back.
    Thanks
    Rinku

  • SOAP ACTION IN SOAP ADAPTER and PROGRAM  IF IN RFC COMMUNICATION CHANNEL

    Hi Gurus,
    Please Explain me what is SOAP action in soap adapter what is the use of it.
    What is the Program ID in the RFC communication channel and what is the use of it.
    Please tell me in  Detail.
    Thanks and Regards,
    RAM.

    Hi,
    Please Explain me what is SOAP action in soap adapter what is the use of it.
    As of W3C definition:
    The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.
    The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.
    Putting things simple, this is an identifier of an operation that you want to execute in the web service (as one web service can offer multiple actions).
    What is the Program ID in the RFC communication channel and what is the use of it.
    Again, this is an identifier for both: RFC sender and receiver systems. It tells the receiver where to listen for connections, and the sender - where to send the data. It works a little bit like a port number in HTTP communication, but with less restrictions.
    Hope this helps,
    Greg

  • Call rfc sender adapter from non-sap systems

    Hi,
    is ist possible to connect to an rfc sender adapter from non-sap systems? I want to use the the RFC-Connector from http://rfcconnector.com, but in the client connect options there is no way to specify the program id.
    Best regards,
    Daniel

    hi,
    you don't need to use RFC type T (with program ID) - you can use whole connection string - just like in the example:
    http://www.rfcconnector.com/documentation/examples/client/#functioncall
    so just specify: host system number etc.
    it should work like that - but let me know as I don't know this RFC connector
    Regards,
    Michal Krawczyk

  • RFC Sender Adapter in XI..Possible??

    Hi All,
    I am trying to send data from XI using RFC Sender Adapter.
    Have done all the configuration, ie created a tcp/ip destination in SM59 and then in the RFC adapter mentioned the program name.
    In Adapter monitoring i can see the adapter working fine.
    When i execute the Function Mouldule i get the following error in SM58.
    parameter JCO.Request was <null> (server: RfcServer[CC_RFC_TX1_OUT]1)
    Can anyone please lemme know if we can send data from XI box using RFC sender adapter.
    Regards,
    Sumit

    Sumit,
    Technically specking this should be possible.. I Havent tried it though..
    So, you are using a Sender RFC to send data from XI to XI itself uh?
    I have tried configuring a Receievr RFC adapter pointing to XI and it has worked fine.
    Also, take a look at these blogs if your config is correct,
    /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    Regards,
    Bhavesh

Maybe you are looking for