About RFCs

Hi all,
        I want to know more about RFCs. What is the diff between transactional async and sync RFCs. Can u tell me vividly so that it can help me in real time.
        Also can u send me some good docs on RFCs in my mail id [email protected]
        Pls experts help me on RFCs and explain me vividly.
        I will reward points.
With regards,
    Abir.

Hai Abhir
Sending system side(SEND--800)
Create function module by using Tcode SE37 or SE80
goto attributes select remote function
activate
Receiving system side(RECE--000)
goto Tcode SM59
here select the R/3 Connections-->click on Create Button
give RFC Desstination : TESTRFC
     Connection Type  : 3 for Connecting two systems
     Description      : Some meaningful Description
Press enter
give Target system Name : SEND
          Language      : EN
          Client        : 800
          user Name     : sapuser
          Password      : xxxxxx
save this connections & click on test connections(f8)
                      & Remote logon(f7)---> it will open a session
                        with client 800 that is your sending system
                        then only your RFC is correct
create a report in SE38 Tcode
data : c1 type i.
data : itab like mara occurs 0 with header line.
call function 'ZRFCFM' destination 'TESTRFC' --->Function Module 'ZRFCFM' your just create at Sending system
     exporting
     importing
     exceptions.
Here are the steps.
SM59 Transaction is used for Connection Establishment with Destination.
When you establish a connection to a client through a destination, the HTTP connection must first be entered in transaction SM59.
There are two types of HTTP connection in transaction SM59: Call transaction SM59 to display the different RFC destinations.
The HTTP connection to the external server (connection type G) and the HTTP connection to the R/3 system (connection type H) are different only in their logon procedures. Their technical settings are the same. To display the technical settings, double-click a connection.
You can choose from three tabs. Under Technical Settings, you can specify the following:
・ Target Host: The host to which you want to connect.
Note that if you are using HTTPS as a protocol, you have to specify the full host name (with domain).
・ Service No.: Here, you specify the port. The destination host must of course be configured in such a way that the specified port “understands” the corresponding protocol (HTTP or HTTPS). See Parameterizing the ICM and the ICM Server Cache.
・ Path Prefix: At the time when the connection to this destination is initiated, the system inserts this sub-path before ~request_uri.
・ HTTP Proxy Options: Here, you can configure a proxy for HTTP connections: You can determine the proxy host and service, as well as users and passwords for the HTTP connection.
The tab page Logon/Security will be different depending on whether you have selected a HTTP connection to an external server (connection type G) or a HTTP connection to an R/3 system (connection type H).
HTTP Connection to an External Server (Connection Type G)
Choose the connection you want to use. You can choose from the following logon procedures:
・ No Logon: The server program does not request a user or password.
・ Basic Authentication: The server program requests a user and password. Basic Authentication is a standard HTTP method for authenticating users. When a user logs on to the target system, he or she provides a user ID and password as authentication. This information is then sent in a header variable as a Base 64-encoded string to the server, through the HTTP connection.
・ SSL Client Certificate: If you use client certificates for authentication, the client authentication is performed through the Secure Sockets Layer (SSL) protocol. In this case, you must also select the SSL Client PSE of the SAP Web AS that contains the relevant certificate for the authentication. The target system must handle the issuer of the SAP Web AS client certificate as a trusted system.
Under Logon/Security, you can also activate SSL to ensure that HTTPS is the protocol used (if you select SSL, make sure that the correct port is entered under Technical Settings). In the security transaction STRUST you can determine which type of SSL client is used. (Getting Started with the Trust Manager, Trust Manager).
The field Authorization for Destination has been implemented as an additional level of protection. We recommend that you specify a user and password for the RFC destination.
HTTP Connection to an R/3 System (Connection Type H)
Here, you can specify more settings for authentication in the target system.
The settings under Technical Settings and Special Options are the same as for connection type G. Under Logon/Security, the connection type H has additional logon procedures. As with external servers, you can activate and deactivate SSL and specify an authorization.
Because the target system is an SAP system, you can set the client and language for the logon as well as the user name and password. If you check Current User, you have to specify the password.
The following authentication procedures are available: Basic Authentication, SAP Standard, and SAP Trusted System, and SSL Client Certificate.
・ HTTP Basic Authentication: Logon with user and password
・ SAP Standard: This procedure uses an RFC logon procedure. The RFC Single Sign-On (SSO) procedure is valid within the one system. The same SAP user (client, language, and user name) is used for logon.
・ SAP Trusted System: Trusted RFC logon to a different SAP system (see Trusted System: Maintaining Trust Relationships Between SAP Systems)).
・ SSL Client Certificate: The SSL protocol enables you to use client certificates for the logon.
Type G/H (SM59)
Timeout:
When sending a HTTP request, you can use this parameter to specify the maximum response time for the connection.
HTTP Setting:
You can use the HTTP version to specify the protocol version of the HTTP request (HTTP 1.0 or 1.1).
Compression:
You can use this option to activate the gzip compression for the request body. This can only be activated in HTTP Version 1.1.
Compressed Response:
In the standard setting, the SAP Web Application Server sends the Accept Encoding field as a header field with the value gzip, if the application server can handle this compression. This notifies the partner that the caller can handle gzip decompression, and that the partner can send compressed data. If you want to prevent a compressed response being sent, choose the option No.
HTTP Cookie:
You can use this option to control the way received cookies are handled.
You can specify the following for cookies:
・ Accept them automatically
・ Reject them automatically
・ Accept or reject them in a prompt
・ Use a handler for the event IF_HTTP_CLIENT~EVENTKIND_HANDLE_COOKIE to process the cookies in the program.
・ In the next section, you can read about the parallelization of requests.
Check this thread
Re: SM59
Thanks & regards
Sreenivasulu P

Similar Messages

  • Question about RFC adapter

    Hi,
    There is this little concept about RFC adapter
    I would like a liitle clarifiaction about..
    Here it goes..
    Let's just say I have made an RFC in R/3.
    The same I have imported In xi.
    now when we say RFC ...By definition
    it is a remote enabled function module.
    We import the "interface" of the Same in Xi
    So if I make changes in the BODY of the RFC in
    R/3... do i need to reimport it in XI.
    Besides when XI's reciver RFC adapter is using the
    Rfc's interface to make changes in R/3
    is it using a Copy of this RFC created in R/3
    I would like to intercep at the point it's doing so...
    tried putting a break point in the body of rfc.
    Another question is regarding RFC sender adapter
    Program ID..tcp Ip protocol.
    Conceptually How does this connectivity takes place
    I tried and it worked ...
    I dunno How to explain this connectivity taking place
    just on the basis of PROGRAM ID...
    Kindly Help

    Hi Deepak,
    +
    >>We import the "interface" of the Same in Xi.So if I make changes in the BODY of the RFC in R/3... do i need to reimport it in XI.+
    Yes you have to.
    >>Another question is regarding RFC sender adapter.Program ID..tcp Ip protocol.Conceptually How does this connectivity takes place I tried and it worked ...I dunno How to explain this connectivity taking place just on the basis of PROGRAM ID...
    ·An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system).
    ·If an RFC call is passed on from any SAP system to this SAP gateway with the option “Connection with a registered program” (with the same program ID), the connection takes place with the corresponding JCo server program.
    http://help.sap.com/saphelp_nw04/helpdata/en/09/c88442a07b0e53e10000000a155106/content.htm
    Hope this will clarify your doubts.
    Regards
    Suraj

  • About RFC's

    Hi Experts,
         I want to know more about RFC's .
         How to work on RFC's
         Examples on RFC's
         Doc's on RFC's
    Please let me know all these
    Regards
    khanna

    Hi ,
    <b>RFC:</b>Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
    <b>Synchronous RFC:</b>
    The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
    <b><b>Transactional RFC (tRFC) and Queued RFC (qRFC</b>).</b> tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
    <b>Transactional RFC:</b>
    If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
    To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
    <b>Queued RFC:</b>When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
    For more information on RFC, please go through the link.
    http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
    Regards,
    Bhanu

  • About rfc concept

    hi gurus,
    Can any body explain me about the rfc concept.
    Thanks.

    Hi Rangamma,
    Check this info.
    These are the types of RFC
    Asynchronous RFC (aRFC)
    Synchronous RFC (sRFC)
    Transactional RFC (tRFC)
    Queued RFC (qRFC)
    Parallel RFC (pRFC)
    Asynchronous RFC :
    This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .
    Transactional RFC
    This let you group one or more function module call together o tRFC LUW and ensure that fucnction module within LUW is called once . In contrast to aRFC and sRFC the tRFC belonging to tRFC LUW are executed in order .
    tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
    1.Executed in the order in which they are called
    2.Executed in the same program context in the target system
    3.Run as a single transaction: they are either committed or rolled back as a unit.
    Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved
    Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
    • When the caller starts an asynchronous RFC, the called server must be available to accept the request.
    The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
    • Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
    • The calling program can receive results from the asynchronous RFC.
    You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the function’s result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
    RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
    IMPORTING
    TABLES
    EXCEPTIONS
    The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
    Transactional RFC (tRFC) and Queued RFC (qRFC).
    tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
    Transactional RFC:
    If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
    To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
    Disadvantages of tRFC
    - tRFC processes all LUWs independent of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
    - In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
    Queued RFC:
    When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
    Therefore, Queued RFC is better than Transactional RFC.
    Remote Function Call:
    RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
    RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
    RFCs manage the communication process, parameter transfer and error handling.
    http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
    Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
    Synchronous RFC:
    The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
    Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
    Transactional RFC:
    If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
    To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
    Queued RFC:
    When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
    For more information on RFC, please go through the link.
    http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
    Have a look at this link.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
    Rewards some points if it is helpful.
    Rgds,
    P.Naganjana Reddy

  • Doubt about RFC Destination in FILE to IDOC Async scenario

    hi
    In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
    For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
    Any specific reason.
    Thanks in advance.

    First you need to have a clear understading of how the idoc adapters works.
    In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
    In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that  u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
    In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
    Hope this answers your ques.
    cheers
    *Raj*
    *POINTS IF SATISFIED WITH ANSWER.

  • About RFC Adapter

    hi
    Expert's
    when i am configure sender RFC ADAPTER i am facing problem so plz help me
    in comm channel
    Rfc:server parameters
    application server gatway: it host name of sender system(sap abap)
    application server service: it..........................?
    wher can i get the host name of sap system
    and server service?
    RFC:MATAATA REPOSITROY PARAMETERS:
    APPLICATION SEVER NAME:
    SYSTEM NO:
    Thanks&regards
    upendra

    Hi,
    >>APPLICATION SEVER NAME:
    login to your SAP system, you can find frm system - status or when you login to ur SAP system, you can find at the right corner(tool bar)
    >>SYSTEM NO:
    usually it is "00"
    Regards

  • About RFC and BAPI

    Hello Masters,
                 What Makes the exact difference between RFC and BAPIs. Both can perfom same thing. BAPI uses the RFCs only. Then how can it justify?
    Thank you

    RFC:
    RFC --- > Function module and general will be used to make call to function
    sending the function (XI has RFC adapter)
    BAPI:
    BAPI ---> Other version of RFC (Objected oriented) mostly we will use for Sync
    calls (Mostly in XI using proxies we will call BAPI's)
    Refer these links for more details:
    http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
    http://www.sap-img.com/fu033.htm
    BAPI Vs IDOC - in detail
    http://searchsap.techtarget.com/tip/1,289483,sid21_gci824860,00.html
    /thread/127699 [original link is broken]
    IDOC,RFC,BAPI
    Re: When and Why we use BAPI, RFC and IDOC.. in XI
    Diff... between  ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify
    idoc and bapi
    Difference among  IDOCS,BAPI,RFC?
    http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
    Differences Between RFC & BAPIS
    RFC Vs BAPI
    For more details:
    refer this thread.
    What are idocs, BAPI, RFC?
    BAPI is nothing but the Business process programing interface which are standard and stable and these are store in the business object repository.
    Standardized programming interface that enables external applications to access business processes and data in an SAP System
    RFC is the remote function call which is used to call the function remotely which may be in same system or ather system
    its also used communication between SAP systems , between SAP systems ,external systems.
    idoc and bapi
    Difference among  IDOCS,BAPI,RFC?
    http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
    Differences Between RFC & BAPIS
    RFC Vs BAPI
    http://www.sap-img.com/abap/ale-bapi.htm
    RFC means remote function call,
    these are the function modules which can help u to access across the sap and from sap to third party front end,
    BAPI means Business application programing interface which is the RFC enable function module and uses in OOPS concept.
    RFC ,IDoc and BAPI
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
    This is a short description of BAPI and RFC
    BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
    RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.

  • Hi,about rfc

    The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
    the sentence above appears in the rfc adapter section of online help.
    i was confused for it..
    i think always eoio uses  qRFC
    why is it mapped to tRFC.
    Message was edited by:
            joy zheng

    The statement given in help.sap is correct and confusing
    According to SAP Note 730870 - Q 9
    <i>Messages with exactly once in order (EOIO) were not supported till and including SP10. With SP11 a XI EOIO-messages will result in a normal tRFC call. If a tRFC is send to a SAP-system it will be executed directly (in other words synchronous) plus the tRFC exactly once handling. The order of the messages belonging to one EOIO-queue will be guaranteed by the Adapter Framework messaging layer.</i>
    Regards,
    Prateek

  • Question about rfc sender

    Hello,
    I was reading a help.sap.com site. I don't understand that sentence:
    "The communication channel in which the RFC adapter is defined must be defined for a service of type Business System in the area Service Without Party. In the PCK, you must create an empty party record." from http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
    So this means: I need a Business system. NO Business Service, right?
    And what is meant by empty party record? Does this mean I need to let the partner fields empty?
    thank you.

    Parties are used when u exchange the data between different parties,B2B.
    B2B means Business to Business communication .It is used when there is exchange of information between two different companies or landscape. In case of B2B every party has it own rules which must be followed if we want to communicate between different organization.
    Check out this link:
    http://help.sap.com/saphelp_erp2004/helpdata/en/ca/efb540efe68631e10000000a1550b0/content.htm
    So there lies the answer...
    Regards
    Reward points if useful

  • Hi.about RFC ADAPTER

    can anybody tell me!
    it is either xi calls sender system's function or xi's function is called by sender system for a sender RFC adapter?
    thanks!

    can anyone want to renew answer for the question?
    i am ready to cancel this question!
    i am gonna reward point.
    thanks everyone to answer question!

  • About RFC

    hi, I use a RFC FM to get a file in the target system. In the FM, if I failed to open the file, I give a message:
    messsage s000(00) with 'No file found'.
    stop.
    But when I test, I choose a target, the program is dump, I choose another, there is no message. Can anyone tell me why?

    hi,
    in ur RFC, add exception for 'file not found'.
    so, instead of saying message xxxx....
    say, message xxxx raising exception.
    so when no file is found in target system, control will return to ur original program and no dump will be occuring on ur target system.
    try it out ...
    regards,

  • About RFC creating EBOM using BAPI_MATERIAL_BOM_GROUP_CREATE

    use BAPI_MATERIAL_BOM_GROUP_CREATE to create ebom in RFC function,when call this rfc from visual C++,rfc returned error message "Enter change number-BOM has history requirement".
    But test this rfc in se37,not have any error.
    how to solve this problem?
    pls,help me.

    Hi,
    An authorization object exists (C_STUE_NOH - authorization to edit bills of
    material without change number). This authorization object has only one
    field.
    When you maintain a bill of material with history requirement, the system
    checks whether the user has an authorization for which 'X' is entered in
    this field of object C_STUE_NOH.If this is the case, the system just
    displays a warning message saying that the bill of material has a history
    requirement.
    Otherwise, an error message is displayed.
    have fun

  • Question about RFC 822

    When I send mail with messenger express to [email protected],the attached *.doc file became AIMC362111431111.rfc822
    Any question about messenger express ?
    Thanks!

    1 the version
    root@jt-mail1 # ./imsimta version
    Sun Java(tm) System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)
    libimta.so 6.1 HotFix 0.02 (built 17:36:06, Aug 25 2004)
    SunOS jt-mail1 5.9 Generic_112233-11 sun4u sparc SUNW,Sun-Fire-880
    root@jt-mail1 #
    2 I send a mail with a attached file name 'test.doc' to [email protected],so I want to see this mail with attached file 'test.doc'.
    But now I see the attached file became: AIMC362111431111.rfc822
    That means 'test.doc' becames 'AIMC362111431111.rfc822' .
    ?

  • About RFC connection

    At the time of GR posting this runtime message occurs
    No RFC destination is defined for SAP Global Trade Services
    Thanks
    Regards
    Anukul
    Edited by: ANU GIR on Nov 10, 2008 10:52 AM

    Hi,
    Check in Sap market Market Place , You will Sap notes for this Error ,
    Also check this [Thread|http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/posting-goods-issue-error-message_type_x-no-rfc-connection-is-defined-for-sap-global-trade-services-2198467#]
    [Thread|No RFC destination is defined for SAP Global Trade Services;
    [Thread|HI SAP Friends;
    Rhea.

  • About RFC and R/3

    Dear experts,
    I am using java along with JCO to connect to SAP and retrieve data from a particular table after every 10secs.Data get retrieved in microsecs.Next cycle comes after another 10 secs and this way
    process continues.Mean data gets retrieved , then 10secs break then once again data gets retrieved and so on........infinite loop..
    However i haven't experience any problem so long.But still i want to confirm if this could be
    causing any extra overheads on SAP R/3 server.
    Thanx in advance..

    Hi Adiyata
    No it should cause any overheads in SAP server .
    But a good idead can be instead of running it after every 10 seconds ,if possible try to pick up all the records in one shot and them againg pick it up after a gap of few hrs coz i do believe that your SAP system might be talking to some other systems also.
    Regards
    Neha

Maybe you are looking for