RFC user in Sm59 on sender system - no access to XI

Hello,
we want to implement an IDOC scenario.
So we added a RFC connection on the sender system and added a user here
which is copied from PIAPPLUSER on our PI 7.0.
The connection test is successful with
- remote login
but not successful with
- authorization test (STRG F4).
Message in trace was: wrong password used.
But we are sure that the pwd is correct. We tried this with three different users and the result is for each of them the same.
Any help is appreciated.
Regards
Dirk

Steffen/ Dirk,
Not a bug. You can find the reason for this wiered behaviour in this thead.
Re: Problem with RFC Destination in SM59
Regards,
Jai Shankar

Similar Messages

Password inconsistancy issue with RFC users in ECC 6.0 System after upgrade

Hi,
We have upgraded the system from 4.7 to ECC 6.0, but facing the password inconsistancy problem for RFC users. We have set the parameters like "login/min_password_lng" as "8" and "login/password_downwards_compatibility" as "3" & RFC user Type is "system". Could you please suggest how to resolve the password inconsistancy issue.

Hi Chandan,
you need to run the txn. SECSTORE and there it will shows you all the RFCs that have inconsistent passwords. Please maintain the correct passwords there.
In case the existing passwords are no longer acceptable due to new security policies as per the new SAP version, you will have to change the password from SU01.
Regards,
Shitij

Authorization Required for RFC user in R/3-APO system.

Could you please help regarding one authorization issue. I want to know the authorization required for one RFC user. Now this RFC user used for RFC connection of SAP R/3 - SAP APO system. user type is given dialog type and SAP_ALL profile has been given to this user id. Now I have to remove SAP_ALL from this user id in R/3 and APO system and provide the required the authorization in R/3 and APO system.
Regard
Auroshikha

The RFC authorisation depends completely on what the user is doing (ALEREMOTE?). We can't tell you what RFC auths your connection requires.
There is a guide to doing this here: https://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections

Standard roles, groups, profiles of a rfc-user

hi,
can anybody tell me please, which are the standard roles, groups and profiles of a rfc-user in our sap xi-system?
thanks.
regards
Stefan

Hi,
Check the links for authorizations.
http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
also check if your user have this roles in abap stack TECODE su01
SAP_XI_ADMINISTRATOR
SAP_XI_CONFIGURATOR
SAP_XI_CONTENT_ORGANIZER
SAP_XI_DEVELOPER
SAP_XI_DISPLAY_USER
SAP_XI_MONITOR
SAP_ALM_ADMINISTRATOR
SAP_J2EE_ADMIN
SAP_SLD_ADMINISTRATOR
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_XI_ADMINISTRATOR_ABAP
SAP_XI_ADMINISTRATOR_J2EE
SAP_XI_CONFIGURATOR_ABAP
SAP_XI_CONFIGURATOR_J2EE
SAP_XI_ID_SERV_USER
SAP_XI_IR_SERV_USER
SAP_XI_RWB_SERV_USER
SAP_ALM_CUSTOMIZER
SAP_BC_BASIS_ADMIN
SAP_BC_BASIS_MONITORING
ARG_XI_DEV
Thanks,
Vijaya.
Edited

SMSY creates RFC user as "Communication" user type

Transaction SMSY was used to create RFC destinations to all satellite systems. In the SMSY wizard, it was requested that the RFC be created as well. After both RFC user and destination were created, it was perceived that the RFC user is of type "Communication".
According to SAP Note 622464, "Communication" user will require the user to modify the password after it has expired. Therefore, I ask:
1. Why does SMSY creates RFC user of type "Communication" instead of "System"?
2. Is there any harm if the RFC user is updated from "Communication" to "System"?

Hello,
'Communication' users are used to 'communicate' ! So they require dialog login (like here in these RFCs) and which they can do and for what they are defined i.e. to login or to make communcation possible via RFCs
'System' users are used to handle the background tasks which do not require dialog login across SAP systems or via RFCs. In other words, system user is not a dialog user and hence can't act as a user in RFCs to communicate acrosss SAP systems !
Hence,
1. SMSY creates 'communcation users'
2. if the RFC user is updated as the system user, then no 'dialog login' and hence 'no communication'

Re: System segmentattion access violation

There is a special utility you must run which will clean the environment
repository. It is located under the following directory:
%{FORTE_ROOT}/install/diag/bin/
It is called envedit
The command works like this:
%FORTE_ROOT%/install/diag/bin/envedit -fs -fr
%FORTE_ROOT%/sysdata/envrepos/<envrepos_name>
You can use the -i option to specifiy a script to run. Such a script will
need to look like this:
# envedit script for cleaning the environment repositories
setworkspace SystemMgr
open
browse
compactrepos
quit
quit
This will clean and compact your environment repository. Make sure that yo
ur environment is offline before you attempt this.
Mark Musgrove
Object Technologies. Inc.
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on 06/29/99 03:58:06 PM
To: Mark Musgrove/BCS/BBS/BLS@BLS
cc: ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw,
forte-users@O1=Internet/DD.RFC-822=forte-users\@sageit.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com (bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id OAA1038
9
for <[email protected]>; Tue, 29 Jun 1999 14:56:37 -0
500 (CDT)
Received: from web502.yahoomail.com ([128.11.68.69])
by carnac.bst.bellsouth.com (Netscape Messaging Server 3.52)
with SMTP id AAA3C12 for <[email protected]>;
Tue, 29 Jun 1999 14:56:03 -0500
Received: from [206.49.176.243] by web502.yahoomail.com; Tue, 29 Jun 1999 1
2:58:06 PDT
Message-ID: <[email protected]>
Date: Tue, 29 Jun 1999 12:58:06 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
Cc: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mark,
We have tried # 1. It does not work.
How do I clean the environment repository?
Thanks
Jorge
--- [email protected] wrote:
This type of segmentation violation is due to an
environment manager
repository corruption. One of the three options
below will fix it(listed
from easiest solution to most difficult). If the
first two do not work,
the third one will always fix the problem.
1. Shutdown and restart the environment.
2. If #1 does not fix the problem, then your
environment repository has
become corrupted. Shutdown the environment and
clean your environment
repository. This will fix your corruption problem
about 75 % of the time.
3. If #2 does not correct your error, then the
environment is corrupted
beyond repair. You will need to delete your current
environment repository
and rebuild it. Sometimes you can rebuild it using
an export of your
current environment(bootstrap). Many times though
the current corrupted
environment will not successfully allow you to
export the environment
definition. In this case, you will have to rebuild
your environment from
scratch.
Hope this helps...
Mark Musgrove
Object Technologies, Inc
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on
06/26/99 12:05:55 AM
To:
forte-users@O1=Internet/DD.RFC-822=forte-users\@SageIT.com@omgw
cc:
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com
(bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6
(PHNE_17135)/8.8.6) with ESMTP id XAA0132
8
for <[email protected]>; Fri,
25 Jun 1999 23:45:53 -0
500 (CDT)
Received: from pebble.SageIT.com ([206.169.110.3])
by carnac.bst.bellsouth.com (Netscape
Messaging Server 3.52)
with SMTP id AAA64AA for
<[email protected]>;
Fri, 25 Jun 1999 23:45:20 -0500
Received: (from sync@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3783 for forte-users-outgoing; Fri, 25 Jun 1999
20:51:51 -0700
Received: (from uucp@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3767 for <[email protected]>; Fri, 25 Jun 1999
20:51:46 -0700
Received: from web501.yahoomail.com(128.11.68.68) by
pebble.sagesoln.com vi
a smap (V2.0)
id xma013762; Fri, 25 Jun 99 20:51:31 -0700
Message-ID:
<[email protected]>
Received: from [206.49.176.243] by
web501.yahoomail.com; Fri, 25 Jun 1999 2
1:05:55 PDT
Date: Fri, 25 Jun 1999 21:05:55 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [email protected]
Precedence: bulk
Reply-To: Jorge Espinoza <[email protected]>
Hello :
We're try connect with our Central Server Node and
have a problem, if we're make the connection with
Escript this is
succesfull, but if we're connected again with
Econsole , Launcher
Distributed or Forte Distributed then this
connection display the
following error
NLM Startup is Complete - Partition's Locale is 'c'
Loading partition FTLaunch_cl0_Client built on
03-Sep-1998 00:37:56.
There is no manager active for node FORTE1.
Type Service Flags Level
err sh * 255
cfg sp 8 255
cfg em 2 2
FTLaunch_cl0: Configuring node agent.
FTLaunch_cl0: Opening configuration repository
bt:c:\forte\sysdata\envrepos\fort
e1.
FTLaunch_cl0: Attached to manager for node FORTE1.
Type Service Flags Level
err sh * 255
cfg em 2 2
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation
in the Forte
executable:
ftexec Version 3.0.J.1
Windows NT
Forte Application Environment (tm), Forte Runtime
Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and
its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws
of the United
States.
Wed Sep 2 22:53:49 1998
Fault at 25-Jun-1999 13:23:56, pid '180', node
'FORTE1':
User Name: Administrador
Machine Name: FORTE1 with 1 CPU(s)
OS version 4.0
Loading symbols for ...
c:\forte\install\bin\QQRP.dll
c:\forte\install\bin\QQCT.dll
c:\forte\install\bin\QQSH.dll
c:\forte\install\bin\QQKN.dll
c:\forte\install\bin\QQSM.dll
c:\forte\install\bin\ftexec.exe
c:\forte\install\bin\QQDO.dll
c:\forte\install\bin\QQCM.dll
c:\forte\install\bin\QQFO.dll
c:\forte\install\bin\QQDS.dll
c:\forte\install\bin\qqtlnt.dll
c:\forte\install\bin\w3tpwss.dll
c:\forte\install\bin\qqem.dll
c:\forte\install\bin\QQDD.dll
c:\forte\install\bin\QQRT.dll
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\rasadhlp.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\System32\spool\DRIVERS\W32X86\2\RASDDUI.DLL
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
qqem 026e2c5d (0130bac0,00000001,00000000,013b8aa0)
QQSM 003b238a (0130bac0,013b8aa0,013f0001,013f4768)
QQKN 0024d5f1 (0130bac0,013b8aa0,013f0001,013f4748)
QQKN 00250915 (0130bac0,013b8aa0,013f4730,013f4748)
QQDO 00432d96 (0130bac0,0209fd40,000000d0,013365b8)
=== message truncated ===
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

There is a special utility you must run which will clean the environment
repository. It is located under the following directory:
%{FORTE_ROOT}/install/diag/bin/
It is called envedit
The command works like this:
%FORTE_ROOT%/install/diag/bin/envedit -fs -fr
%FORTE_ROOT%/sysdata/envrepos/<envrepos_name>
You can use the -i option to specifiy a script to run. Such a script will
need to look like this:
# envedit script for cleaning the environment repositories
setworkspace SystemMgr
open
browse
compactrepos
quit
quit
This will clean and compact your environment repository. Make sure that yo
ur environment is offline before you attempt this.
Mark Musgrove
Object Technologies. Inc.
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on 06/29/99 03:58:06 PM
To: Mark Musgrove/BCS/BBS/BLS@BLS
cc: ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw,
forte-users@O1=Internet/DD.RFC-822=forte-users\@sageit.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com (bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id OAA1038
9
for <[email protected]>; Tue, 29 Jun 1999 14:56:37 -0
500 (CDT)
Received: from web502.yahoomail.com ([128.11.68.69])
by carnac.bst.bellsouth.com (Netscape Messaging Server 3.52)
with SMTP id AAA3C12 for <[email protected]>;
Tue, 29 Jun 1999 14:56:03 -0500
Received: from [206.49.176.243] by web502.yahoomail.com; Tue, 29 Jun 1999 1
2:58:06 PDT
Message-ID: <[email protected]>
Date: Tue, 29 Jun 1999 12:58:06 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
Cc: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mark,
We have tried # 1. It does not work.
How do I clean the environment repository?
Thanks
Jorge
--- [email protected] wrote:
This type of segmentation violation is due to an
environment manager
repository corruption. One of the three options
below will fix it(listed
from easiest solution to most difficult). If the
first two do not work,
the third one will always fix the problem.
1. Shutdown and restart the environment.
2. If #1 does not fix the problem, then your
environment repository has
become corrupted. Shutdown the environment and
clean your environment
repository. This will fix your corruption problem
about 75 % of the time.
3. If #2 does not correct your error, then the
environment is corrupted
beyond repair. You will need to delete your current
environment repository
and rebuild it. Sometimes you can rebuild it using
an export of your
current environment(bootstrap). Many times though
the current corrupted
environment will not successfully allow you to
export the environment
definition. In this case, you will have to rebuild
your environment from
scratch.
Hope this helps...
Mark Musgrove
Object Technologies, Inc
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on
06/26/99 12:05:55 AM
To:
forte-users@O1=Internet/DD.RFC-822=forte-users\@SageIT.com@omgw
cc:
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com
(bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6
(PHNE_17135)/8.8.6) with ESMTP id XAA0132
8
for <[email protected]>; Fri,
25 Jun 1999 23:45:53 -0
500 (CDT)
Received: from pebble.SageIT.com ([206.169.110.3])
by carnac.bst.bellsouth.com (Netscape
Messaging Server 3.52)
with SMTP id AAA64AA for
<[email protected]>;
Fri, 25 Jun 1999 23:45:20 -0500
Received: (from sync@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3783 for forte-users-outgoing; Fri, 25 Jun 1999
20:51:51 -0700
Received: (from uucp@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3767 for <[email protected]>; Fri, 25 Jun 1999
20:51:46 -0700
Received: from web501.yahoomail.com(128.11.68.68) by
pebble.sagesoln.com vi
a smap (V2.0)
id xma013762; Fri, 25 Jun 99 20:51:31 -0700
Message-ID:
<[email protected]>
Received: from [206.49.176.243] by
web501.yahoomail.com; Fri, 25 Jun 1999 2
1:05:55 PDT
Date: Fri, 25 Jun 1999 21:05:55 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [email protected]
Precedence: bulk
Reply-To: Jorge Espinoza <[email protected]>
Hello :
We're try connect with our Central Server Node and
have a problem, if we're make the connection with
Escript this is
succesfull, but if we're connected again with
Econsole , Launcher
Distributed or Forte Distributed then this
connection display the
following error
NLM Startup is Complete - Partition's Locale is 'c'
Loading partition FTLaunch_cl0_Client built on
03-Sep-1998 00:37:56.
There is no manager active for node FORTE1.
Type Service Flags Level
err sh * 255
cfg sp 8 255
cfg em 2 2
FTLaunch_cl0: Configuring node agent.
FTLaunch_cl0: Opening configuration repository
bt:c:\forte\sysdata\envrepos\fort
e1.
FTLaunch_cl0: Attached to manager for node FORTE1.
Type Service Flags Level
err sh * 255
cfg em 2 2
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation
in the Forte
executable:
ftexec Version 3.0.J.1
Windows NT
Forte Application Environment (tm), Forte Runtime
Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and
its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws
of the United
States.
Wed Sep 2 22:53:49 1998
Fault at 25-Jun-1999 13:23:56, pid '180', node
'FORTE1':
User Name: Administrador
Machine Name: FORTE1 with 1 CPU(s)
OS version 4.0
Loading symbols for ...
c:\forte\install\bin\QQRP.dll
c:\forte\install\bin\QQCT.dll
c:\forte\install\bin\QQSH.dll
c:\forte\install\bin\QQKN.dll
c:\forte\install\bin\QQSM.dll
c:\forte\install\bin\ftexec.exe
c:\forte\install\bin\QQDO.dll
c:\forte\install\bin\QQCM.dll
c:\forte\install\bin\QQFO.dll
c:\forte\install\bin\QQDS.dll
c:\forte\install\bin\qqtlnt.dll
c:\forte\install\bin\w3tpwss.dll
c:\forte\install\bin\qqem.dll
c:\forte\install\bin\QQDD.dll
c:\forte\install\bin\QQRT.dll
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\rasadhlp.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\System32\spool\DRIVERS\W32X86\2\RASDDUI.DLL
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
qqem 026e2c5d (0130bac0,00000001,00000000,013b8aa0)
QQSM 003b238a (0130bac0,013b8aa0,013f0001,013f4768)
QQKN 0024d5f1 (0130bac0,013b8aa0,013f0001,013f4748)
QQKN 00250915 (0130bac0,013b8aa0,013f4730,013f4748)
QQDO 00432d96 (0130bac0,0209fd40,000000d0,013365b8)
=== message truncated ===
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

RFC Adapter - Where to Register Rfc2XmbService (Sender System or XI ?)

Experts,
I have the following scenario:
R3 --> RFC_ADAPTER --> XI --> SOAP --> THIRD_PARTY
My specific question is, In which system do I need to register the Rfc2XmbService program. Is this done in the R3 system or in the XI system.
If it is done in the R3 system then where is it done cause there is no J2EE administration tool in R3.
Could someone explain exactly what this registration concept is.
Thanks and appreciate any help in advance.
- Ravi
--- I have figured this one out already. The program needs to be registered in XI and Not the sender system.
Thanks
Message was edited by: ravi kumar

Hello,
the Rfc2XmbService registers itself when you activate the RFC adapter in the Configuration but you can preallocate it through the Visual Admin.
Further by default are logging for sync calls not enabled, e.g. you don't see anything in SXMB_MONI.
Therefore go to SXMB_ADM and the Integration Configuration option and under the RUNTIME specific option create an entry for
RUNTIME LOGGING_SYNC 1 (0 is default).
Also make sure that the rfc adapter is activate in the AdapterFramework overview. On the target system call transaction SMGW and go to logged on clients to see if you see the Rfc2Xmb Service. Then in SM59 of the R/3 system you should have an entry pointing to the Rfc2Xmb service and a test should give you an idea if it works.
I'm doing R/3 4.6c -> XI 3.0 -> R/3 Enterprise about 20 BAPIs, no issue.
I hope this helps.
Stefan

RFC users locked after system copy in production system

Hi,
BW_User,MDBTC(RFC users) system users were locked in our BI Production system at the same time system copy activity was running in the Quality system(production to quality) so as per our colleagues concern after system copy they started Quality system with out changing background work-process 0 so some jobs were triggered which were copied from production system.
Is there any cause to lock RFC users in production system for system copy? If there is any other reason where we can check logs
Thanks
Jalandhar Reddy

Hi,
Well maybe i am wrong to analyze your problem .
Anyway I faced this issue to in our system before and we found that one background job was running in a system that has basically prompting an RFC connection to another system. In the t.code SM59 and there was wrong password was put in.We just reset the password and it was worked fine.
You can try for this..
Regards
Bhuban
RKFL

RFC\BAPI to login into remote system with user id's in that system

Dear Friends,
I have a requirement to run a job .In that job, i need to login into other remote system with the user id's in that system.
May I know, is there any remote function module or BAPI available.
Let me know how to solve this issue.
Regards,
Madhu..!!

Hi Divakar,
As far as I know, there isn’t this feature of remote test in VS2013.
I suggest that you could submit this feature request:
http://visualstudio.uservoice.com/forums/121579-visual-studio. The Visual Studio product team is listening to user voice there. You can send your idea there so the others can vote it. If you submit this suggestion, you might post that link here which will
benefit others who has the similar issue
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

RFC User for satellite systems

Hello Gurus,
I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
Many thanks in advance for your help
Miloslav Pudil
IDS Scheer
Prague
Czech Republic

>
Miloslav Pudil wrote:
> I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
> Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
Hi Miloslav,
Technically, it will work that you define one common RFC user in your SolMan for communication (RFC BACK destination) from all connected managed systems.
BUT, I would never recommend it.
Once a managed system cause issues in your SolMan, you are not able (or at least it's much more difficult) to identify the managed system. Same happens, if a invalid password in the BACK destination leads to a locked user.
My recommendation: Spend the extra effort in creating a user per managed system. Operation will be much easier later.
See also this guide:
[Activating EarlyWatch Alert [EWA] in End Customeru2019s System |http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000567342009E]
Best regards,
Ruediger

SAP Sender System (RFC scenario)

I don't understand who will initialize process of sending a message in case of RFC sender system.
I need to configure RFC destination in SAP System, configure XI RFC Sender Channel.
Will XI invoke RFC function on sender system? or Will sender system invoke RFC function on XI?
How to set up scheduling?

hi Denis,
>>>>Will XI invoke RFC function on sender system? or Will sender system invoke RFC function on XI?
if you want to send from the SAP then you have to
invoke the RFC youself
call function
desination
in background
commit work.
then all the values will go to the XI
that you passed in your RFC call
Regards,
michal

System Landscape RFC User

Hi,
I have a simple question. I would like to be able to monitor my erp system(on another host) from solman. Using wizard, In the set-up system landscape-> create system step, under the main instance selection, what should I choose to add my erp system?
Plug Ins for Satellite Systems or Agents for Satellite Systems
Thank you.

Hi,
This info i took it from help library.
If you want the ATP check to be performed in SAP APO but triggered from SAP R/3, make sure when
defining the RFC connection of the SAP APO system in SAP R/3 that you use a user ID for the SAP APO
system that was created there as a dialog user.
Thanks,
nandha

Verify Sender System - Communication channel RFC sender

Dear all,
We would like to select the option "Verify sender system" in our communication channel, RFC sender.
Do you know the correct parameters that we need to set? SYS-ID, CLIENT?
It would be nice to have an example.
Our PI version: PI7.11
Thanks you very much in advance.
Best Regards,
Olivier Vanderperre

For non-SAP systems we do not set these parameters.....we do not check this option Verify Sender System
Is it to trust other non SAP systems
actually we do not set this option for non-SAP system becuase it is not possible to set the SID and Client details in the sender application....whereas when it is an SAP system we are able to set the details and hence verify them in XI/ PI.
Edited by: abhishek salvi on Mar 26, 2010 1:14 PM

RFC USER USER TYPE- SYSTEM/SERVICE?

Hi,
We are using CTP method of GATP.
Currently our user type for RFCUSER (Usermentioned in rfc destination) is service? It allows dialog mode this is security concern for us as RFC USER as all authorisations.
When we changed it to system user it is giving error while triggering GATP. Also there is dump in SCM system with message
"DYNPRO_SEND_IN_BACKGROUND"
"/SAPAPO/SAPLATP4" or " "
"SYSTEM-EXIT".
pls. suggest solution
Regards,
Santosh

Hi,
This info i took it from help library.
If you want the ATP check to be performed in SAP APO but triggered from SAP R/3, make sure when
defining the RFC connection of the SAP APO system in SAP R/3 that you use a user ID for the SAP APO
system that was created there as a dialog user.
Thanks,
nandha

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

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

RFC user in Sm59 on sender system - no access to XI

Similar Messages

Maybe you are looking for