Session created by RFC Destination don't close.

Hi Experts
I create an RFC Destination in NetWeaver 7.2, and i use this destination to access some RFC from CAF project.
The problem is when i access the RFC, the ECC create a session to the user and don't close this session.
After some time i have a lot of session created in ECC. The session in ECC should be closed, because i get some error when there are a lot of session with the same user opened in ECC.
I create the destination in NWA - Destination.
Could someone help to solve this?
Regards
Marcos Brandã

Not anwsered.

Similar Messages

How to create a RFC destination for extracting data to HANA

Hello All,
Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

Hi Venkatesh,
In SM59 t.code we create RFC destinations.
Go thru the video link for creating RFC destinations step by step
How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

Create a RFC destination with default pass word

hi folk,
I've a Z-program which creates a RFC destionation (SM59) with a default password. The RFC destination has been created successfully with all the necessary fields, but the pass word is not aticve.
I'm using this fucntion module to scramble the pass word.
slen = STRLEN( p_p_prfcpw ).
SET EXTENDED CHECK OFF.
    CALL FUNCTION 'HTTP_SCRAMBLE'
      EXPORTING
        SOURCE            = p_p_prfcpw
        sourcelen         = slen
        key               = key
     IMPORTING
       DESTINATION       = p_pw
I've got this message from SM59.
Error in conversion of user password for destination A3
Message no. SR131
Diagnosis
The upgrade to SAP Release 7.0 starts an XPRA program that converts passwords to secure storage. In certain cases, you may need to skip this procedure (for example, due to database locks during the upgrade). This can cause the passwords to become invalid.
Procedure
Enter the user password again.
Any clues what is going wrong or how to solve this situation?
Best regards
Linhng

hi Roberto,
Everything is working except the pass word is not "converted" when I create the RFC destination in my z-program.
So my question is still how do I create a RFC destination with the "correct" pass word.
I've tried the function module HTTP_SCRAMBLE to convert the pw and also without the FM.
Best regards
LinhNg

How to logoff a session created by RFC

Hi All,
I'm using an RFC to call a funtion in another server and is working right now using a logical destination, but I have a problem with the session, everytime when the user execute this funtion to a come back to R/3, CRM server keep the session alive. I would like to know if the is a way to close the session when the user comes back to R/3.
This is the fuction that I'm using
CALL FUNCTION 'Z_FTT_ZTB1_FIND_RECORD' DESTINATION l_logsys
            EXPORTING
              i_claim          = ztsgendat-zzclaim
            IMPORTING
              brc_documentid   = l_bapiguid
              brc_documentclas = l_bapidclass.
Thanks in advance
Kind Regards
Alexis

call this FM to close RFC connection
call function 'RFC_CONNECTION_CLOSE'
exporting
    destination = dest
exceptions
    others      = 1.
Regards
Raja

Best practice for creating RFC destination entries for 3rd parties(Biztalk)

Hi,
We are on SAP ECC 6 and we have been creating multiple RFC destination entries for the external 3rd party applications such as Biz-talk and others using TCP/IP connection type and sharing the programid.
The RFC connections with IDOC as data flow have been made using Synchronous mode for time critical ones(few) and majority through asynchronous mode for others. The RFC destination entries have been created for many interfaces which have unique RFC destinations with its corresponding ports defined in SAP.
We have both inbound and outbound connectivity.with the large number of RFC destinations being added we wanted to review the same. We wanted to check with others who had encountered similar situation and were keen to learn their experiences.
We also wanted to know if there are any best practices to optimise on number of RFC destinations.
Here were a few suggestions we had in mind to tackle the same.
1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
I have done checks on SAP best practices website, sap oss notes and help pages but could not get specific information I was after.
I do understand we can have as unlimited number of RFC destinations and maximum connections using appropriate profile parameters for gateway, RFC, client connections, additional app servers.
I would appreciate if you can suggest the best architecture or practice to achieve RFC destinations in an optimized manner.
Thanks in advance
Sam

Not easy to give a perfect answer
1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
-> be careful if you have multi cllients ( for example in acceptance) RFC's are client independ but ports are not! you could run in to trouble
2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
-> could be the best solution... its easier to create partner profiles and the control record will contain the correct partner.
3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
-> consider this option 2.
We send to you messagebroker with 1 RFC destination , sending multiple idoctypes, different partners , different ports.

How to create RFC Destination without using SM59?

Hello all:
We are troubleshooting an issue. An user created a RFC destination. He claims that he did not use SM59. We checked his access and do not have SM59 in his roles.
He configured VIRSA FireFighter. During the configuration, he created RFC destination. Document says use SM59 or contact BASIS Admin. He claims that he used a config table and he don't remember the config table name. RFC screen shows his ID as creator of the RFC.
We are trying to understand how an RFC can be created (outside of SM59) and plug the security hole in the environment.
Any insights would be appreciated.
--Anand

The FireFighter solution changes the RFC destination of the service user "on the fly" without S_TCODE checks for 'SM59'. But if I can remember correctly when looking into this, it does not create the RFC destination (in SM59) "on the fly".
> He claims that he used a config table and he don't remember the config table name.
Theoretically this is possible - a config table to define the name of the destination, and then create it if it does not exist yet (when used).
Otherwise, see SAP note 587410 and restrict (remove) his authority for the test environment (concentrate on S_DEVELOP, not S_TCODE - as you have also experienced).
Cheers,
Julius

Creating RFC Destination in SAP R/3

Trying to create an RFC destination in SAP R/3. Looked at few articles in creating them, but I am getting error while testing. It says that the "Program" couldn't not be found. I tried with all options, "Registered in Server Program", "Start on Application Server" etc.,
Is there a place to register a "Program"? Is this program specific to my XI server? How should this program be created or registered.
Any help is greatly appreciated!
Thanks
Satya

one more hit:
http://server:port/rwb/index.jsp
message monitoring
BTW
you have created everything in XI repository & configured everything in xi directory haven't you?
if not you can try this document:
"Validating a Connection Between R/3 and SAP XI with RFC"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/validating a connection between sap r3 and sap xi with rfc.pdf
by Sridhar Rajan Natarajan
Regards,
michal
Message was edited by: Michal Krawczyk

RFC - XI - WEBSERVICES scenario - Where to create RFC Destination

Hi Experts
For my RFC - XI - WEBSERVICES scenario, I have to create one TCP/IP RFC destination on R/3 system with the following details
RFC Destination Name    : XXXX
Connection Type            : T (TCP/IP)
Activation Type              : u201CRegistered Server Programu201D
Program ID                      : YYYY
Gateway Host                : R/3 Details ..??
Gateway Service           : R/3 Details ..??
My Function Module (Remote-Enabled) - u201CZZZZu201D is defined in R/3 System.
This Function Module should be communicated with the target system i.e. NW XI system
As per the Note from SAP Help: To be able to communicate using RFC, you need to define the target systems as RFC destinations in the sending system(R/3)
Target system u2013 XI Server
Sending system u2013 R/3 System
Are my details provided are good enough as per my explanation? Please guide me in this regard.
QUESTION : Where exactly do I need to create the RFC Destination(SM59)? on R/3 side or on XI side?

Refer the following link-
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1636235450DB01012070359836134304End?blog=/pub/wlg/1438
what are the inputs should be given to Gateway Host and Gateway Service while creating RFC Destination??
Open transaction SMGW on the R/3 system and choose
Goto -> Parameters -> Display. Beneath Attributes there will be the
entries 'gateway hostname' and 'gateway service'.#

Creating RFC destination in Visual Administrator results in error

Hi.
I am trying to set up ESS and MSS on a EP 6.0 with SP15.
According to a Post-installation guide for SLD i have to create a RFC destination, but when i save the settings i get the following error: Error changing bundel's properties, see LOG for details!.
And when i try to start the RFC destination i get the following error: Error starting bundle, see LOG for details!
Have anybody encountered this problem, and if so, can you give me a hint to what the problem might be?
Regards Liselotte

hi
I am also running into this error, and this is preventing me from completing my xi configuration as after i create the bundle..and select start..i get a msg "error starting bundle see log for details.."
what log do i see...?
and a test connection from sm59 also fails..
any help on this is appreciated.
Regards
Ravi

Crm xif creating rfc destination

Hi All,
I am going through the documentation of FM CRMXIF_PARTNER_SAVE.
I am stuck at the following point:
1. Create a suitable RFC destination in the SAP IMG Define Target Systems for RFC Calls (for example,a TCP/IP connection to the Business Connector).
My requirement is as follows:
I have to integrate the CRM SAP and salesforce for real time synchronisation of Business Partner data.
How to create an RFC destination ?
I am absolutely new to this.
Looking forward to ur support
Regards
Shilpi

Hi Shilpi,
There are various issues here. But, just to answer about RFC creation, you can do it through Tcode SM59. But, if you are new to this, I would suggest that you request your basis person to create that for you since it should be his responsibility.
From which system are you planning to call this FM? Usually people use this for data load in CRM in which case you dont need an RFC destination.
Regards,
Alin

RFC destination error in posting 3rd party payment in 4.7 FI system

Hi,
We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
The error says "An RFC destination could not be specified for the logical system HD1CLNT014
    Message no. B1550
Diagnosis
    An RFC destination should be specified for the logical system
    HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
    local logical system and this system is not included in the relevant
    Customizing tables.
Procedure
    Check:
        -   RFC destination
           -Port definition
         -oubound partner profile of message type SYNCH for this logical system
We checked our configuration for all Logical system and RFC destination and everything seems fine.
Any help in this regard is appreciated.
Thanks
Kesav

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

Creation of RFC destination for SAP-Access Connectivity

Hi,
       I want to create a RFC destination for SAP-Access connectivity.
Can I get some help regarding it's connection type,activation type and gateway options required for the same.
Regrads,
Anthony D'souza

Hi
Please see the following:
1. Create an entry in Trxn DBCA for SQL Server in SAP, you are creating a database connection for the SQL server in SAP.
2. You use this connection, and write Native SQL stmnts...between EXECSQL...ENDEXEC to fetch the data..and then normal ABAP statements to put that data into your ztable.
TABLE DBCON Entry can be like this...depends on your External database..
CON_NAME          Raj                      Logical name for connection
DBMS                   MSS                   Microsoft SQL Server
USER_NAME        <User name>       For SQL Server
PASSWORD         <password>         " "
CON_ENV             MSSQL_SERVER=<server> MSSQL_DBNAME=<database name>
DB_RECO                 Availability type for an open database connect
FUNCTION z_houston_connect.
""Local interface:
EXEC SQL.
CONNECT TO 'RAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
*- Get the data from MS-SQL Server
EXEC SQL.
open C1 for
select
l.loc_id,
l.loc_name,
a.acc_id,
a.acc_name,
d.person
from ho_loc_mast as l
inner join snd_acc_mast as a on l.loc_id = a.loc_id
inner join snd_acc_addr as d on a.loc_id = d.loc_id and
a.acc_id = d.acc_id
where l.loc_id = '001'
ENDEXEC.
DO.
EXEC SQL.
FETCH NEXT C1 into :wa-c_locid, :wa-c_locname, :wa-c_acc_id, :wa-c_acc_name, :wa-c_person
ENDEXEC.
IF sy-subrc = 0.
PERFORM loop_output.
ELSE.
EXIT.
ENDIF.
ENDDO.
EXEC SQL.
CLOSE C1
ENDEXEC.
ENDFUNCTION.
Regards,
Raj

Error in Local Message System: RFC destination 10.189.98.10 does not exist.

Error in Local Message System: RFC destination 10.189.98.10 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam going inside the tcode SM30 in the satellite system and entering the destination ip of solution manager system and after that when iam creating a message from HELP-CREATE SUPPORT MESSAGE, then it is throwing the following error.
Can anyone please help me in the above issue.
Regards,
Mirza Kaleemulla Baig.

Hi Mirza,
For the RFC destination don't enter the IP address,enter the RFC name,somthing like SM_SP1CLNT200_BACK which is maintained in sm59.
Revert for any clarifications.
Thanks and Regards,
Avinash.

Decreasing amount of RFC-Destinations when using UD-Connect?

Hello,
I created an RFC-Destination in sm59 as well as JCO RFC Provider and used the SAP manual for UD-Connect/JDBC to a "foreign" Sybase-DB. The Connection is working properly and all DB-data is accessible, but our cutomer claims that there are more than 25 parallel rfc-connections from our Web AS to his Sybase-DB. My question is: How can I decrease the amount of parallel connections, because I don't think 25 connections to Sybase-DB are necessary. I know there is the maxConnection-Property in JCO RFC Provider but this parameter is globally affecting all RFC-connections and not only those that are associated with the Sybase-DB.
Is there actually a way to customize the amount of parallel connection via JDBC?
Best regards
Danny

Hi,
use transaction "smqs", select destination and click on registration change max number of connections.
Try to define rfc server group to control connections ...
Regards
Ben

RFC destination Could not be SPecified for Logical System

Hello there
i am traying to costomize Transaction Luancher for some of the report which is been devloped in ECC (wich is ARD 100)
when on Transaction launcher Wizard--> techincal
i am having a logical system as ARD100(my r.3 system where report is devloped and which is connected to CRM )
while chosing the OBJ.TYpe :   and Method:
it says shows three erroe :
1) RFC destination could not be specified for the logical system ARD100
2) Object type and Method is not available
i have checked RFC , in SM59 entriesu2026u2026 There is an RFC named ARD100 and the connection test works. I also did an authorization test and it also works. I also checked to make sure the logical system name ARD100 exists
could you please help me to resolved the same
Regards
Rajiv

Hi Rajeev,
In a system landscape it's important and necessary to use the logical system names consistently throughout all systems!
Therefore please make sure, that you always use the same name for a logical system in all systems (CRM and R/3 systems).
The following steps are required before a RFC call is made from the CRM system to the R/3 system :
    o Use transaction SM59 to create an RFC destinations for the remote
       system.
    o Use transaction BD54 to create the logical system.
    o Use transaction BD97 to link the RFC destination created in SM59
       with the logical system created in BD54.
I hope this helps.
Best Regards
Gavin

Session created by RFC Destination don't close.

Similar Messages

Maybe you are looking for