Rfc with trusted systems

Hello!
I configure system landscape via SMSY and I try to generation rfc connection for added system using wizard.
My system is Solution Manager 4.0,  client is 001.
In future I hope to use solman for SP download approving.
What client in trusted system I need to generate rfc-connections?

HI,
Antonina Mukhanova   wrote :
In future I hope to use solman for SP download approving.
What client in trusted system I need to generate rfc-connections?
It doest not matter to what client you are connecting using the wizard for RFC in SMSY.
sp stacks is not client dependent.
Regards,
VIJAY.

Similar Messages

  • RFC with External system

    Hi,
    We are trying to develop interface with external system to calculate the shipping costs for a delivery. We will establish RFC connection between SAP and External system.
    Do we need SAP .NET connector to send and receive data from/to SAP. SAO shouls act as client and external system as server. If we have to use SAP .NET connectore, can anyone explain me the detailed process of using SAP .NET connector and connecting to external system.If there is anyother way without using SAP .NET connector, i.e by using RFC function modules, can you please xplain that process too. What is the program ID for RFC destination in SM59?
    I appreciate your help.
    Thanks,
    Ashok.

    setting the program id you need a person with the knowledge of both the system, with the current input it will be difficult to help with that.
    since you are in 4.6C the available options are
    1. DCOM connector
    2. .net connect
    3. JCO
    4. or a plain http call to your external system.
    Regards
    Raja

  • Creation of trusted RFCs between two systems

    Hai,
    Can anyone help me to create TRUSTED RFC between two systems ie Solution Manager and the Production. To carry out Service desk facility.

    Dear Mohan,
    You can create RFC's in the Solution manager system using T-Code SMSY. there you find all your installed systems select the system from the left hand side under Landscape Components click on Application Server ABAP on the right hand side you will find a tab client in this screen select the client for which you want to create TRFC. Go to change mode and click on the button Generate RFC with Assistance. Carry out the wizard for creating the RFC's...

  • No trusted/login RFC connection for system BCP in TA SMSY

    Hi,
    i got this error  Early Watch Report  for only production System.
    No trusted/login RFC connection for system BCP in TA SMSY
    Amit

    HI,
    I hope the error message is straight forward.
    Please Check whether you have established RFC connections to the BPC system and the same is avaiable under the RFC connections in TRXn SMSY-Your system -.Test the connections in SM59-BPCs-> READ and Trusted RFCs.
    If its not present, Generate the RFCs again manually.
    Hope this helps.
    Revert for any issues.
    Thanks,
    Jagan
    Edited by: jagadheeshan govindasamy on Oct 9, 2009 3:24 PM

  • CALL_FUNCTION_SINGLE_LOGIN_REJ- No authorization to log on as a Trusted System (L- RC=1 T-RC=1).

    Hi All,
    i have created a trusted connection(say system A_100 and B_100,---100 is a client) as per SAP note 128447 - Trusted/trusting systems
    I have all required authorisation i.e s_rfcacl,S_rfc ,s_rfc_tt.
    i am able to remote logon from system B_100 to system A_100 ,but issue in when i try to logon from system A_100 to system B_100.
    error is -
    No authorization to log on as a Trusted System (L- RC=1 T-RC=1).
    i can see run time error in system B_100 as with user SAPSYS and client 000(why it is showing this user and client )
    CALL_FUNCTION_SINGLE_LOGIN_REJ
    Details-
    Category               Installation Errors
    Runtime Errors         CALL_FUNCTION_SINGLE_LOGIN_REJ
    Date and Time          08.08.2014 09:07:04
    Short text
         No authorization to log on as a Trusted System (L-RC=1 T-RC=1).
    What happened?
         The current program had to be terminated because of an
         error when installing the R/3 System.
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         An RFC call (Remote Function Call) was send with an invalid user ID
         "XXXX " or the caller system is not registered as a Trusted System in the
         target system.
    Information on where terminated
        Termination occurred in the ABAP program "SAPMSSY1" - in
         "REMOTE_FUNCTION_CALL".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 113
        of the (Include) program "SAPMSSY1".
    Source Code Extract
    Line  SourceCde
       83   COMMUNICATION SEND ID convid BUFFER header.
       84   IF sy-subrc EQ 0.
       85     PERFORM (sy-xform) IN PROGRAM (sy-xprog).
       86   ELSE.
       87     MESSAGE a800.
       88   ENDIF.
       89 ENDFORM.                    "cpic_call
       90
       91 *&---------------------------------------------------------------------*
       92 *&      Form  remote_function_call
       93 *&---------------------------------------------------------------------*
       94 *       text
       95 *----------------------------------------------------------------------*
       96 *      -->VALUE      text
       97 *      -->(TYPE)     text
       98 *----------------------------------------------------------------------*
       99 FORM remote_function_call USING value(type).
      100   DATA rc             TYPE i VALUE 0.
      101   DATA: l_syxform     TYPE syxform,
      102         l_syxprog     TYPE syxprog,
      103         l_cbe         TYPE i.
      104
      105 * necessary variables for class based exceptions
      106   DATA: l_root        TYPE REF TO cx_root.
      107
      108   DO.
    109 *
    110 * with ID 'CLException' we determine, whether the caller is
    111 * class based excptions or not
    112 *
    >>>>     CALL 'RfcImport' ID 'Type'        FIELD type
    114                      ID 'SYXForm'     FIELD l_syxform
    115                      ID 'SYXProg'     FIELD l_syxprog
    116                      ID 'CLException' FIELD l_cbe.
    117
    118     IF l_syxprog = 'JAVA'.
    119       SYSTEM-CALL plugin
    120                   ID 'JAVA' VALUE 'FORW_JAVA'
    121                   ID 'RC'   VALUE RC.
    122 *   if there is no rollout on the JAVA side which
    123 *   rolls both, JAVA and ABAP, we return to the
    124 *   C-Stack and reach this point
    125
    126 *   in case there was an rollout, the ABAP-C stack is lost
    127 *   and we jump direkt to this point
    128
    129 *   here we trigger the rollout on this Abap side with
    130 *   the following statement
    131       SYSTEM-CALL plugin
    132                   ID 'JAVA' VALUE 'ROLL_OUT'
    I have also referred sap note-1627901 - Trusted RFC troubleshooting
    No luck.
    Do let me know if additional information is needed .
    Kind Regards,
    Sumit

    Hi Sumit
    1.  Is this both system Support pack level are same?
    2. As you said that you SAP_Basis 7.31 - support package level?
    3. Have you check the SAP note 128447 - Trusted/trusting systems they are given ABAP runtime correction  2021691 - CALL_FUNCTION_SINGLE_LOGIN_REJ and trusted RC=1
    4.
    one question -  why it is working in system B and not in system A.
    Its may be software bug for that they give ABAP runtime correction
    Regards
    Sriram

  • Error in Local Message System: No authorization to logon as trusted system

    Dear all,
    When I am posting the message in Production system which I have configured with my solution manager
    I am getting the error like "Error in Local Message System: No authorization to logon as trusted system. So trusted message can not be posted"
    I checked with SM59 which I created the RFC destination, in that i selected for both the system ie Solution manager as well Production system 'Trusted System=Y'
    Please suggest me how to solve this issue
    Regards
    Sudharshan

    Hi,
    please use the search function.
    There are ALOT of topics regarding Trusted RFCs, table BCOS_CUST, RFC Back Destination to Sol Man and so on.
    /cheers

  • ERROR IN CREATING TRUSTED SYSTEMS

    Dear Gurus,
    When creating the trusted systems between to sap systems, we are getting the below error.
    "No authorization to log on as a trusted system (Trusted RC=0)."
    We created the trusted system entry in SMt1 and the RFC check is working fine(both test connection & authorization test).
    Even i am able to login to the remote system. But when i check the system in SMt2, i get the above mentioned error.
    Could you please let me know on how to resolve the above error.
    Thanks & Regards
    Surendranath

    Hi,
    Trusting Transaction SMT2                                                     
    The trusting transaction SMT2 (or SM59 ® RFC ® Trusting Systems) constructs a list of all trusting systems that have been established for this trusted system. Here, a logon and authorization check for the current user and client is performed, using the destination TRUSTING_SYSTEM@S00 that has been automatically created.       
    This basically corresponds to transaction SM51, if you use Remote Login to perform a logon on a different application server.                                                                               
    If problems occur while setting the destination TRUSTING_SYSTEM@S00 (such as host name or service information), you either have to create a new destination for your needs, and then enter the host name or service information using SAP router strings, or adjust the network settings of the server. To correct the problem in transaction SMT2, you have to adjust the network configuration of the server. As this transaction is only to be used for test purposes, in this case you could also choose to ignore the error.                                                               
    To perform a logon as a different user or client, you have to create a new RFC destination with a trusted option set.                                                                 
    In this scenario, the following error text in SMT2 can be ignored:
    No authorization to log on as a trusted system (Trusted RC=0)
    If the host name contains the character '_' (as in "my_host"), then the generation of the related trusting system destination may lead to incorrect settings. This problem can be corrected by implementing Support Package SAPKB46D09 (see below). For earlier releases, the changes required to correct the problem can be made manually.
    Continue with:
    Configuring System Resources for Parallel RFC, tRFC, and qRFC
    Rgds,
    Suman

  • Authorization to logon as trusted system (Trust

    Hello everybody,
    I want to configure the RFC between the solman and IDES server. so i have done the following things
    1. Create a user sapuser in solman and Ides server with the Authorizations, SAP_SUPPDESK_CREATE,SAP_SV_FDB_NOTIF_BC_ADMIN,ZSAP_S_RFCACL,ZSAP_SOL_SERVTRANS_CREATE
    2. Create the RFC named SOLTRUSTED in IDes with  detail as 
                  Target Host       :-               solman
                  I.P                        :-              192.168.1.4
                  System No         :-              00
                  Trusted System :              No
    After that i have test the connection its working, Same as Remote Logon, . Logon screen asking for user name and password is also working fine.
    3. execute the T.cdoe SMT1 create a  Trusted System  SOL with details as
       Trusted System   SOL
      Technical settings
          RFC Destination       SOLTRUSTED
          Authentication type   3
         message server        solman
    Trusting system
       Trusting system       RIS
       Application server    ides_RIS_08
    here when select Entry-->authorization check -->trusting system here 2 times logon screen appear for solman logging and generate the Error " Error when opening an RFC connection 
    I have also set the authorization for the object  S_RFCACL with required field value as *
    Also i have check the TRUSTING_SYSTEM@SOL Rfc, then the connection test successfully done but at Remote Logon No, generate error as - authorization to logon as trusted system (Trust
    So please guide/suggest me that any missing or additional steps missing for configure the trusted and trusting system
    Thanks
    Ganesh

    Hello,
    As per your suggestion, i have two system Solman and IDES, I want to connect solman and Ides
    1. i have create the RFC in IDES
              RFC name             SOLTRUSTED
              Connection type   3
              Target Host           SOLMAN
              System No            00
        ON clicking Connection Testing - successfully
        On clicking Remote Loging, Logon screen is display, on entering Client, Username, and password successfully logon to the solution manager.
              IP address        192.168.1.4 
    As per suggetion of second step, I have been trying to create the trusted system, i enter the name SOLTRUSTED,at the logon screen enter the client 901, user name and password
    Now on the Trusted System means on Solution Manager
    create the RFC named RISCLNT999
             Connection type = 3 and descrption
       enter the target host - ides
                 system number - 08
                 trusted system = yes
                 client  -999
                 check the current user option
          and SAVE
    All the setting i have done, but from the IDes server when i use the command Smt1 and select Entry-->Authorization check -->Trusting system, it display logon to solman screen 2 times display the error message "Error when opening an RFC connection"
    Entry-->Authorization check -->Current server, it display logon to solman screen display the error message "No authorization to logon as trusted system (Trusted RC=0)"
    I have metion in previous message that i was maintain all the necessary authorization.
    so please suggest me how to solve the authorization problem?
    Thanks
    Ganesh

  • Auto-logout of dialog type users connected via trusted system

    Hello,
    We have System AAA. In this system we have users 1234 and 4321 of dialog type.
    User 1234 logs in via SAP GUI.
    User 4321 logs in via trusted system BBB.
    We have set rdisp/gui_auto_logout to 30 seconds.
    User 1234 is logged off after 30 seconds.
    User 4321 is never logged off.
    How can we force user 4321 to be automatically logged off after 30 seconds?
    Peter

    With (Trusted) RFC calls in general you are calling a function module and not a transaction. Okay, the FM might call a transaction in a new task and present it to look exactly like a transaction which had been started locally, but if you look in SM04 on that server then you will see that the protocol is not DIAG but rather RFC for the sessions.
    So, what you can do for such current user context trusted RFC calls which are dialog capable and interactive with the SAPGui, is simply call FM RFC_CLOSE_CONNECTION whenever you want the connection to the current user to be closed.
    Of course, if the user is fast and your security design is sub-optimal, then even 30 seconds might not help you (from a security perspective).
    I remember mention a while ago about a profile parameter which gives you an option to timeout an idle but open RFC connection. I tried a quick search but did not find it again. If you keep an eye out for the legendary term "Wolfgang" when searching together with "auto" "timeout" "logout" etc terms then you should be able to find it with some patience.
    Please also see the OSS notes on RFC_CLOSE_CONNECTION. You will find more infos there and possible the optional parameter as well.
    Cheers,
    Julius

  • No authorization to logon as trusted system (Trust ed RC=0)

    Hi Guys,
    I am working in CHARM implementation and i am facing a problem while importing the transport request from development to quality system.
    once i select the pass correction to test action in urgent correction the system is giving an warning message(No import into test system has taken place yet).
    When i go to task plan there the system is showing the transport request is succesfully released, but Import transport request as RED.
    Description of the Error: System cancel RFC destination SM_QASCLNT410_TRUSTED, Call TMW_SET_PROJECT_SWITCHES: No authorization to logon as trusted system (Trust ed RC=0).
    But when i do the pass correctio to test with SAP_ALL in Quality system it is successfully importing to quality system.
    I have also assigned S_RFCACL to developer role in quality system. kindly give ur valuable inputs as it is very urgent.
    Thanks&Regards
    Raju

    Penmetsa,
      Interesting name - trusted connections are somewhat interesting to work with - please check them by using the 'Remote Logon' button with the username check set to current user (if you are using a specific user, there is no real reason to use a trusted connection).  When doing this, follow OSS Note: 128447 which is all the troubleshooting for Trusted Connections with all the return codes.
      From what you are showing with the RC=0, that is ususally authority - you probably don't have the role setup right on the QA system.  Personally, I wouldn't bundle this because there are different flavors of this role that should be assigned to certain users.  You should go check with your Security people for the best way to assign the proper credentials to end-users.  A improperly configured S_RFCACL will allow one to access a remote system with a different userid!!  Which is not really a good thing to have as a possiblity for daring developers that are looking for interesting things to play with.
      Anyhow - hope that helps, if it answers your question, please set the thread to answered.

  • Trusted system entry already exists for system SOL

    Hi,
    Im trying to add a second trusted system with smt1 transaction but the thing is that i've already have an identical SID for another system so i get the "Trusted system entry already exists for system SOL" message.
    is there any way to solve this??
    thanks in advance.
    regards.

    In  SM59 - in the RFC in question - Press "Technical Settings" tab - then press "Yes" to Load Balancing - this will populate the "Target Host" field.
    Then make sure that you here enter the system data for the Target System (Default it will display the Host System data which you will need to replace)
    Then go back to SMT1 - Press the "Create" button - and in the Wizard you enter the RFC connection as before... Now it should work.
    Regards,
    Lars

  • Loading failed from ECC to BW due to sharing port with XI system

    Hi,
    I need some help here, currently my company has 2 sandbox systems, one for ECC(R/3) and another one is for XI/BI netweaver 2004s. Since the BI box is shared with XI, we have problem everytime we load the data to the BI master data/ods/cube .
    It seems there is something wrong with the data port setting/configuration.
    The error message that was given in RSMO transaction always showed:
    "Errors while sending packages from OLTP to BI
    Diagnosis
    No IDocs could be sent to BI using RFC.
    System Response
    There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
    Further analysis:
    Check the TRFC log.
    You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
    Error handling:
    If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system."
    Now after checking this in TRFC in source system and BI system, there was nothing wrong, no IDOCs was listed there or got hold up. We have checked the user authorization with our basis here, we use id called PIREMOTE that has same setting as SAP ALEREMOTE id. So we are not sure what went wrong since the connection in SM59 seemed to be working fine.
    When we checked into Details tab at the RSMO screen for detail explanation, we got the following message under Transfer (IDOCs and TRFC) section:
    "Request IDoc : Application document not posted
    Info IDoc 1 : sent, not arrived ; Data passed to port OK
    Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n "
    We believed that the error could be related to the partner profile and data port setting in WE20/WE21 in source system (DEVCLNT150) and BI system (NWDCLNT001). It seems that the data is pointed to XI port rather than BI port since the ECC-XI work demo worked fine and ECC-BI work demo ended up in trouble.
    The R/3 system partner profile (DEVCLNT150) and BI system partner profile (NWDCLNT001) has setting as following
    in outbound parameters:
    with Message type RSINFO (IDOC basic type RSINFO) and RSSEND (IDOC basic type ZSNB004),
    both message types are pointing to BI data port (NWDCLNT001)
    The inbound parameters cointains message type RSRQST (process code RSRQ).
    I have been trying to search the solution for weeks, but i couldn't find the right solution.
    I tried to change the partner profile setting but instead it didn't work for XI and BI so i set the setting back to original after complaint raised by XI team.
    We don't want to lose the current connection that we have for XI system since they use it for XI demo, but in the same time we need to send data to BI system for our demo purposes.
    Please advice any steps or solutions that work. Do we need to clean up some SAP tables that setup the port or do we need to run some transactions?
    Any opinions are welcomed.
    Thanks,
    Hendy

    For - planning , please take a look at SAP Extended Financial Planning rapid-deployment solution:  G/L Financial Planning module.   This RDS captures best practice integration from BPC 10 NW to SAP G/L.  This RDS (including content and documentation) is free to licensed customers of SAP BPC.   This RDS leverages the 0FIGL_C10 cube mentioned above.
      https://service.sap.com/public/rds-epm-planning
    For consolidation, please take a look at SAP Financial Close & Disclosure Management rapid-deployment solution.   This RDS captures best practice integration from BPC 10 NW to SAP G/L.  This RDS (including content and documentation) is also free to licensed customers of SAP BPC.
    https://service.sap.com/public/rds-epm-fcdm
    Note:  You will require an SAP ServiceMarketplace ID (S-ID) to download the underlying SAP RDS content and documentation.
    The documentation of RDS will discuss the how/why of best practice integration.  You can also contact me direct at [email protected] for consultation.
    We are also in the process of rolling out the updated 2015 free training on these two RDS.  Please register at this link and you will be sent an invite.
    https://www.surveymonkey.com/s/878J92K
    If the link is inactive at some point after this post, please contact [email protected]

  • ERROR with Source System in BI

    Hi,
    I replicated the datasources from DEV to BI. They replicated just fine. I can even see it in BI. I then tried to activate the datasource (i created the datasource from a view ) but it gave me a run time error :
    ASSIGN_LENGTH_0 Short dump has not been completely restored..too big.
    I then tried to go into the source system and tried to activate that and it said:
    Source System DEV300 is inactive
    BI Unknown in system
    BI IDoc type ZSBC019 is not the same as source system IDoc type
    The following errors occured in the source syaytem:
    Entry in inbound table not found
    Entry in outbound table not found
    Result of the destination check: No authorization to logon as trusted system
    What could have went wrong?
    Thanks

    Did you try activating the source system in RSA1 ..right click and choose active.
    if this doesnt work then you might want to check the inbound and outbound entries in we20 transaction code for the source system. If you have authorization. Or you need to check with your BASIS to set that up for you.

  • Call RFC with DLL created with DCOM CONNECTOR

    I try to call a RFC with a DLL that i created with the SAP R/3 DCOM CONNECTOR (Release 4.5.B):
    My external soft calls the DLL, which calls the RFC, which calls a transaction (Call Transaction Mode N, Update S)...
    When i test the RFC in SAP (SE37), it's OK.
    But when i call the RFC with my soft (and with the DLL), the Call Transaction returns sy-subrc = 1.001 (the methode "AdviseRfcGuiSink" included in the DLL allows me to launch the debugging with my external soft).
    I found no SAP notes about this problem.
    If you met the same problem, could you help me ?
    Thanks.
    Julien.

    Some Years later I have the same Problem.
    As discripet in the post before - first I've got an error in the Method "CreateNewRow()" where the Method wants to return "return new byte[]()". Well I don't know why the .Net-Connector creates that code - but it looks strange to me.
    The origin Code is:
        /// <summary>
        /// Creates an empty new row of type byte[].
        /// </summary>
        /// <returns>The newbyte[].</returns>
           public override object CreateNewRow()
                return new byte[]();;
    With Changing that method I've got the same Error as in the post before:
    System exception thrown while marshaling RFCTYPE_XMLDATAto .NET type.
    Does someone has found a solution for that kind of Problem?

  • How to set up trusted system or ip in NW CE 7.1

    Hi all,
    I am running on NW CE 7.1, and I want to know if NW allows setting up trusted system or ip. If so, is there any documentation about it?
    Thanks for your help in advance.

    Hi,
    what do you mean by "trusted system"?
    For instance, you can use the CE as a producer in your EP 7.0 consumer portal with SSO. You exchange server certificates and so create a trust between these 2 servers. This is also be possible between CE and ABAP (CE is consuming an ABAP service).
    To do so, it's the standard process: export the certificate of CE and import it into the target system
    br,
    Tobias

Maybe you are looking for