Password of SAP* in Client 100

i Created a new client .
What is the passwrod used to login to the client
PAssword for SAp* as pass is not working
Pls help me how to proceed
Thanks in Advance

Hi Balaji,
first execute RZ10 and select the instance profile in "exteneded maintaince" mode. then edit and add this parameter "login/no_automatic_user_sapstar" and set the value to "0" to activate this.
then execute the following query @ SQL prompt.
"delete from <HOSTNAME>.<SID>.<object_owner>.USR02 where BNAME='SAP*' and MANDT='100';" and after try loging with password "PASS" remember its case sensitive.
hope this will help you!
with BR,
Rajesh
 award suitable points

Similar Messages

Changing the Password of SAP*

hI ,
 I forgot my SAP * password now I want to delete it from DB level
Database is MSSQL 2005 .Guide me with your detailed procedure
Stephen

Hello Lena,
Se38 > Creta a program
*& Report ZPSWRESET
*& Basis - 10.03.2007 - ikarayaka
REPORT ZPSWRESET_V1.
Tables: usr02, t000.
data: passwd like usr02-bcode.
parameters: user like usr02-bname.
select single * from usr02 where bname = user.
if sy-subrc <> 0.
write: / user, 'user does not exist!'. exit.
endif.
passwd = usr02-bcode.
clear usr02.
write: / 'The password of', user, 'updated in client:'.
select * from t000 where mandt <> '066' and mandt <> sy-mandt.
select * from usr02 client specified where mandt = t000-mandt and
bname = user.
 write: / usr02-mandt.
 usr02-bcode = passwd.
 usr02-ltime = sy-uzeit.
 usr02-bcda1 = usr02-bcda2 = usr02-bcda3 = sy-datum.
 usr02-bcda4 = usr02-bcda5 = sy-datum.
 usr02-UFLAG = ''. "change to the target client
 update usr02 client specified.
endselect.
endselect.
Changing the Password of SAP* ( all client )
Regards
ismail KARAYAKA

Moving sap form from client 100 to client 120

hi all,
i have created a form in client 100 . how to move the form to client 120.

Bharath,
If it is a script ask your Basis team to move the request from 100 to 120( seems you have both 100 and 120 in the same server).Scripts are Client Dependent.I guess you will not be having authorisation to SCC1.
If it is a Smartform it will automatically get update in 120.Smartforms are Client Independent.

SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

Hello,
after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".
Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".
After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).
I also connected the CRM development and CRM quality assurance system without a problem.
For client 000 everything worked fine, the RFC destinations were created and a green light is shown.
Now the problem is to connect the productive client 100:
The log for Activity RFC Connection says:
The corresponding dev_rfc tracefile says:
**** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work
**** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL
======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)
ABAP Programm: SAPLSM_SETUP_API (Transaction: )
Called function module: FUNCTION_EXISTS
User: SOLMAN_ADMIN (Client: 001)
Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})
EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1
EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7
But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.
Does anyone have a clue?
Kind regards
Rüdiger Höckel

Hello Ranjith,
thanks for your quick response.
The ST-A/PI software component is the same on all systems: 01Q_700 #2.
SolMan system: SM3
CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).
I also tried the recommendation found in the SAP Community Network
(http://scn.sap.com/thread/3483642) but this didn't help either:
1.Delete system from LMDB.
2.Delete system from SLD of solman.
3.Re- register the system to SLD of solman(rz70 for AS ABAP)
[the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]
4.Now follow the steps in managed system configuration.
The wizard worked fine for client 000 but throws this error for client 100.
I use all the latest installation and configuration guides.
For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.
https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf
Kind regards
Rüdiger
P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

Initial user to login to client 100

I have installed a demo version of SAP NW.
I have created client 100 in client 000.
My question is how do i login to client 100??
I tried SAP* with PASS but coudld not get into..
Any ideas??

Hi ,
If all the users are locked, they can be unlocked by
a)Try this command at ur sql plus query level
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
this will take you to the sqlprompt.
Just execute the earlier commands there.
sqlplus>UPDATE SAP<schema>.usr02 set uflag=0 where mandt=<CLNT NO> and uflag=64;
this statement actually unlocks the users of that particular client. So, try for every client in that sap system.
b) You can delete sap* user
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
sqlplus>DELETE SAP<SID>.usr02 where mandt='CLIENT.NO' and bname=SAP*;
Note:-
After doing this restart the system. So, that a new user with the name "sap" gets generated with password "pass". Provided the parameter is set login/no_automatic_user_sapstar= 0 (Automatic user SAP is permitted).
regards,
kanthi

Can't login to new Client 100

Hi,
I have installed SAP Netweaver 7.0 SR1 SP3 ABAP Trial Version on Windows.
I have defined a new Client 100 with transaction SCC4.
I can't login to this new Client, it fails with message "name or password is incorrect". I have tried multiple credentials.
sap*/minisap
sap*/pass
sap*/06071992
None of them work
Please can you help?
Thanks, Olivier

> I can't login to this new Client, it fails with message "name or password is incorrect". I have tried multiple credentials.
> sap*/minisap
> sap*/pass
> sap*/06071992
sap*/pass is the one you need. For this to work you have to set the profile parameter login/no_automatic_user_sapstar to 0 (zero) and restart the instance. This parameter defaults to 1.
see [SAP help|http://help.sap.com/saphelp_nw04s/helpdata/en/22/41c43ac23cef2fe10000000a114084/frameset.htm] for more info.

Initial password for SAP* in SAP NetWeaver 2004s ABAP Edition

Hello,
I have just installed the SAP NetWeaver 2004s ABAP Edition on my PC and I want to setup some new clients to simulate an ALE model.
Does anyone know the initial password for SAP* ?
I have already tried PASS and pass because I know it is case -sensitive now but it did not work.
Thanks a lot.
Wim Van den Wyngaert

Hi,
initial SAP* password is 06071992
DDIC is 19920706

How do we reset password for SAP* and DDIC user in SAP R/3 ECC 6.0?

Hi,
How do we reset password for SAP* and DDIC user in SAP R/3 ECC 6.0?
I tried with acual method as below from client '000':
DELETE FROM USR02 CLIENT SPECIIED WHERE BNAME = 'SAP*' AND MANDT = '001'.
After this when I tried to logon '001' using SAP* with password PASS it is giving the message that Incorrect logon and password.
(Also when I checked for 'SAP*' in 001 it looks like it is not got created as I queried as below:
SELECT SINGLE * FROM USR02 CLIENT SPECIFIED WHERE BNAME = 'SAP*' AND MANDT = '001'.)
Can anybody throw some light on this? RewardS is guranteed for solutions!
-B S B

Hi again:
I forget to tell.
You must restart the system. So, that a new user with the name "sap*" gets generated with password "pass"
Hope this wil help,
Eric

No service for system BC_TREMAx, client 100 in Integration Directory

Hi, I have had this problem and spent to many hours on this. I decided to post the config once I got it working.
I am NOT using the system landscape directory for the java connector -> XI communicaiton.
The SLD is used for XI -> SAP
Scenario: send idocs
SAP Java connector -> SAP XI -> SAP 4.6c
here is the relevant code (the rest of it is in the examples of the java connector):
               System.out.println("setMessageType");
               doc.setMessageType("ACC_DOCUMENT");
                        doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set, otherwise not needed to get file into XI
               doc.setRecipientPartnerType("LS");
               doc.setRecipientPartnerNumber("SE1CLNT500");
               doc.setSenderPort("BC_TREMA");
               doc.setSenderPartnerType("LS");
               doc.setSenderPartnerNumber("BC_TREMA");
               doc.setClient("100");
Inside XI configuration integration builder
Business Service: Service: BC_TREMA
Under the menu Service - Adapter specific identifiers
Idoc Adapter Logical system: BC_TREMA (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
IDoc Adapter and RFC adapter R/3 Sysytem ID: BC_TREMA
Client: 100
On receiver tab:
Name                        NameSpace                               Software componenet
ACC_DOCUMENT.ACC_DOCUMENT01 urn:sap-com:document:sap:idoc:messages TREMA_GLM, 1.0...
On sender tab:
Name                        NameSpace                               Software componenet
ACC_DOCUMENT.ACC_DOCUMENT01 urn:sap-com:document:sap:idoc:messages TREMA_GLM, 1.0...
In IDX1 trans
Port: BC_TREMA
Client: 100
RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
In IDX2 trans
Make sure to import the IDOC type beforehand. If IDOC is not imported you get system error 000 in java connector in SP14.
That was a hard one to track down.
This should be it.
Another example where the difference is the SAP prefix...
               doc.setMessageType("ACC_DOCUMENT");
                  doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
               doc.setRecipientPartnerType("LS");
               doc.setRecipientPartnerNumber("SE1CLNT500");
               doc.setSenderPort("SAP3MA");
               doc.setSenderPartnerType("LS");
               doc.setSenderPartnerNumber("TREMACLNT");
               doc.setClient("100");
Inside XI configuration integration builder
Business Service: Service: TREMACLNT
Under the menu Service - Adapter specific identifiers
Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
Client: 100
On receiver tab:
Name                        NameSpace                               Software componenet
ACC_DOCUMENT.ACC_DOCUMENT01 urn:sap-com:document:sap:idoc:messages TREMA_GLM, 1.0...
On sender tab:
Name                        NameSpace                               Software componenet
ACC_DOCUMENT.ACC_DOCUMENT01 urn:sap-com:document:sap:idoc:messages TREMA_GLM, 1.0...
In IDX1 trans
Port: SAP3MA (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
(a not so well documented feature)
Client: 100
RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
In IDX2 trans
Make sure to import the IDOC type beforehand. If IDOC is not imported you get system error 000 in java connector in SP14.
SE1CLNT500 as a SAP business system setup in the system landscape directory SLD
Receiver determination:
Sender
Service: TREMACLNT
Interface: ACC_DOCUMENT.ACC_DOCUMENT01
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver
Party: *
Service: *
Configured receivers:
Service: SE1CLNT500
After saving you may do the setup in the bottom frame:
Configuration Overview for Receiver Determination
|SE1CLNT500 ->
         ACC_DOCUMENT.ACC_IM_ACC_DOCUMENT Receiver _IDoc to SE1CLNT500
Interface determination
Sender
Service: TREMACLNT
Interface: ACC_DOCUMENT.ACC_DOCUMENT01
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver
Service: SE1CLNT500
Configured inbound interfaces
Name                         Namespace                               Interface mapping Namespace                  Software comp
ACC_DOCUMENT.ACC_DOCUMENT01 urn:sap-com:document:sap:idoc:messages IM_ACC_DOCUMENT   urn:trema-com:trema:trema TREMA_GLM...
Sender agreement
Not needed for IDocs
Receiver agreement
Sender
Service: TREMACLNT
Receiver
Service: SE1CLNT500
Interface: ACC_DOCUMENT.ACC_DOCUMENT01
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver communication channel: Receiver_Idoc_to_SE1CLNT500
Hope this helps someone
/Otto Frost /Capgemini

Hi ,
Create a technical system and bussienss system of type WEB AS ABAP and use this bussiness system for source system in XI and try it.
Thanks & Regards,
Sekhar

Server0 will not start. client 100 does not exist.

On my NetWeaver 7.0 system with Solution Mgr 7.0 (build from IDES 600 image) on a HPUX 11.23 IA & Oracle with Java 1.4.2.15 installed, I'm going thru the basic setup steps for configuring MOPZ and get to the step
Following IMG basic install steps (basic settings->SAP Solution Manager System->System Landscape(SLD)->Specify service for comm. w/ SLD in Visual Admin), unable to connect to J2EE engine via Visual Admin.
The dev_server0 log:
[Thr 6] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 6] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
Std_server0.out log:
===========================================================
Apr 27, 2009 8:14:20 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_73] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed"
. Technical details: Client 100 is not available in this system
I ran JCmon to restart the instance.
cd /usr/sap/SMA/ DVEBMGS00/j2ee/os_lib
jcmon pf= /usr/sap/SMA/SYS/profile/SMA_DVEBMGS00_pax3
20: local Admin.
Restarted instance, but same error, client 100 is not available in this system.
std_server0.out details
===============================================================
Apr 30, 2009 4:24:50 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_97] Fatal: Initialization of ABAP data
source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Client 100 is not available in this system". This message
is critical if it appears during the startup of the AS Java.
Apr 30, 2009 4:24:50 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_97] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Cli
ent 100 is not available in this system
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:445)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
 ... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Cli
ent 100 is not available in this system
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:445)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
 ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Apr 30, 2009 4:24:50 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_97] Fatal: Critical shutdown was invoke
d. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
============================================================
Solution maybe obvious, create a client 100. But server0 was running fine on this node when I first installed Solution Mgr, and it is running fine on my ERP / BI system that II built from the same IDES media, ofwhich it does not have a client 100 and Java WebAS is running fine. Also, able to connect to portal via http://host:50000/irj. Only difference is I have java 1.4.2.20 installed on the BI system.
So is there some other reason why server0 will not come up?

Using the search tool for property name containing "client", the only client defs in the configtool are ume.r3.connection.001-004.client under
cluster-data->Global server configuration->services->com.sap.security.core.ume.service. Values are blank. This is the same on my failing system SMA (SolMgr) and working system BIF(BI system).
The ume.r3.connection.master.client has custom value of 100. I set it to one and restarted the cluster.
The WebAS is up and running again. Don't know what could of changed it to 100.
Thanks for all your help.
-Don.

How to configure sap maxdb client to connect to SAP ERP system (SAP HR)

Hello all,
I am currently installing live cache for SAP ERP HR application(Idoc), can anybody tell me the sequence to proceed to configure SAP livecache with SAP ERP system. i am doing following steps
1. Install SAP DB using installation MAXDB CDs
2. Install SAP Livecache and standalone server SCM 5.0 using SAP ERP master and Livecache dvds.
3. install Livecache client fromSAP ERP master and livecache dvds between SAP ERP and livecache server.
4. configure in LC10, tcode.
but when i press on livecache monitoring in LC10 it gives me following error.
Command: DBMRFC
Parameter: -gsapfive -xsapgw00
SY-SUBRC: 8
Return Code
sap maxdb client

i tried the said things and after that i am getting following error in DB59, first three steps are successful but 4 one is failing.
Test Scope
1. Execute an external operating system command (DBMCLI)
2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC command mode)
3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC session mode)
4. Test the SQL connection (Native SQL at CON_NAME)
Application Server: <hostname>_<SID>_00 ( Windows NT )
1. Connect. test with "dbmcli db_state" Successful
2. Connect. test with command mode "dbmrfc db_state" Successful
3. Connect. test with session mode "dbmrfc db_state" Successful
4. Connect. test with "native SQL" ( LCA ) No connection
 SQL Code: 4008
 POS(1) Unknown user name/password combination
 For detailed information, see the developer trace for work process: 1
please see trace from file dev_rfc and dev_w0 below
log for dev_rfc
**** Trace file opened at 20110107 174356 Eastern Standard Time, SAP-REL 701,0,14 RFC-VER U 3 1016574 MT-SL
======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
ABAP Programm: SAPLARFC (Transaction: )
User: MKUMAR (Client: 800)
Destination: IDOCTEST (handle: 2, , )
SERVER> RFC Server Session (handle: 1, 45030386, {9BAF1AE0-E29B-F1A3-9406-0019B9E204CC})
SERVER> Caller host:
SERVER> Caller transaction code: (Caller Program: SAPLQOWK)
SERVER> Called function module: ARFC_RUN_NOWAIT
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
DEST =IDOCTEST
HOST =%%RFCSERVER%%
PROG =IDOCTEST
Log from dev_w0
A RFC 1485 CONVID 47150684i tried the said things and after that i am getting following error in DB59, first three steps are successfuk but 4 one is failing
trace from file dev_rfc is below
**** Trace file opened at 20110107 174356 Eastern Standard Time, SAP-REL 701,0,14 RFC-VER U 3 1016574 MT-SL
======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
ABAP Programm: SAPLARFC (Transaction: )
User: ABC (Client: 800)
Destination: IDOCTEST (handle: 2, , )
SERVER> RFC Server Session (handle: 1, 45030386, {9BAF1AE0-E29B-F1A3-9406-0019B9E204CC})
SERVER> Caller host:
SERVER> Caller transaction code: (Caller Program: SAPLQOWK)
SERVER> Called function module: ARFC_RUN_NOWAIT
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered
DEST =IDOCTEST
HOST =%%RFCSERVER%%
PROG =IDOCTEST
A RFC 1485 CONVID 47150684
A * CMRC=2 DATA=0 STATUS=0 SAPRC=679 ThSAPOCMINIT
A RFC> ABAP Programm: SAPLARFC (Transaction: )
A RFC> User: abc (Client: 800)
A RFC> Destination: IDOCTEST (handle: 2, , )
A RFC SERVER> RFC Server Session (handle: 1, 47149684, {FDB31AE0-D203-F1C0-9406-0019B9E204CC})
A RFC SERVER> Caller host:
A RFC SERVER> Caller transaction code: (Caller Program: SAPLQOWK)
A RFC SERVER> Called function module: ARFC_RUN_NOWAIT
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
M
M *****************************************************************************
M *
M * LOCATION SAP-Gateway on host <HOSTNAME> / sapgw00
M * ERROR program IDOCTEST not registered
M *
M * TIME Fri Jan 07 18:15:25 2011
M * RELEASE 701
M * COMPONENT SAP-Gateway
M * VERSION 2
M * RC 679
M * MODULE gwr3cpic.c
M * LINE 1778
M * DETAIL TP IDOCTEST not registered
M * COUNTER 715
M *
M *****************************************************************************
M
A RFC 1485 CONVID 47152747
A * CMRC=2 DATA=0 STATUS=0 SAPRC=679 ThSAPOCMINIT
A RFC> ABAP Programm: SAPLARFC (Transaction: )
A RFC> User: ABC (Client: 800)
A RFC> Destination: IDOCTEST (handle: 2, , )
A RFC SERVER> RFC Server Session (handle: 1, 47151731, {FDB31AE0-D203-F1C1-9406-0019B9E204CC})
A RFC SERVER> Caller host:
A RFC SERVER> Caller transaction code: (Caller Program: SAPLQOWK)
A RFC SERVER> Called function module: ARFC_RUN_NOWAIT
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
Mani

Delivery Customizing copy to client 100

Hello,
I have included a add-on SCEMSRV 700 with SP 06 to my Ehp4 ERP system in client 000. As post installation step mentioned in S.note:1173567,Delivery Customizing is imported into client 000 and may have to be copied to other clients. For more information, see Note 337623.
I checked Note 337623 still could not make out what needs to be done for copying this changes in client 000 to client 100(our cutomizing client). We have client 200 and 210 too in this DEV system. Request for valuable suggestion on my next action.Thanks in advance.

Hello,
After you've installed SEM add-on in client 000 - it is available 'cross-client' in your system.
E.g.:
You have 3 standard clients (000, 001, 066) and client 100 (a copy from 000). You install add-on (any) it's standard delivery is immediately available in your system. The only thing you'd probably do (concerning BW) is maintain 'client' value in table RSADMINA:
ta 'SE16' --> table 'RSADMINA' --> field 'BWMANDT' (Unique client in BW).
BR
P.S.
Check SAP Note [522569 - BW: Working in several clients (especially APO 4.x/SCM 4.x)|https://service.sap.com/sap/support/notes/522569]

Password synchronization between more clients

Hello All,
Does anyone know how can I do to synchronize the password of user between more than one client; I explain in 46C I have an abap to write the password wher you are logging into other client of the same SAP instance. If you are logged on client 500 the report write the password of user from client 500 to client 600 and client 000.
This report write in USR02 table (USR02-BCODE = PASSWD)
but in ECC6 this report doesn't running
Does anyone explain why ? may be in ECC6 exist another table or something like that
Thanks in advance for your reply
Bernard
[email protected]

You can try using FIM with PCNS to sync passwords from Domain A to Domain B: https://technet.microsoft.com/en-us/library/jj590203(v=ws.10).aspx
As for Office 365, you can simply implement an ADFS platform and federate it so that your users will be using their AD passwords. It is also possible to sync passwords with DirSync.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Provision UserID/Password from SAP Ssyetm to Non-SAP System

Hi,
I have a requirement to be able to provision UserID & Password from a SAP ECC6 system to a non-SAP thick client application. All interactions between ECC6 & the non-SAP Application will be via SAP PI. (SAP EEC6 <-> SAP PI <-> Non-SAP App)
Our landscape includes:
SAP ECC6
SAP BI
SAP PI
SAP SOLMAN
SAP Portal
non-SAP App
SAP IdM has been ruled out due to budget constraints, Active Directory is not suitable due to the requirement that the non-SAP application must be able to authenticate users if the WAN/LAN is down.
Yes, we could simply maintain the users in both systems, but for the time being that has been deemed not appropriate.
I have thought about using CUA on SOLMAN to provision to the SAP Systems & then use SAP PI somehow to provision to the non-SAP App, but I have no idea how to pass the raw user password through SAP PI.
If anyone has any ideas or can point me to links where I can do further research would be much appreciated.
Thanks in advance,
Stephen Hall

The search term "password AND synchronize" will help you further to find "flamewars" from the past.
You cannot send "raw" passwords from CUA, as the password is represented by a "one way" hash which is not decryptable by mortals, but rather the "raw" password is encrypted and the hashes are compared locally. Non-SAP systems cannot do this... (bar trial-and-error).
A better option would be to use a SSO mechanism. This is very easy within SAP.
For bi-directional authentication with non-SAP you will face some challanges...
The easiest option is to re-use a PKI certificate based authentication or re-use the native Kerberos authentication available for Windows bases PCs.
In the SAP --> non-SAP direction you can consider using a verification library to extract the user name - but that is not "state of the art" and if such a UID should be encrypted then have fun...
In the non-SAP --> SAP direction you are best off forgeting about the infrastructure trust or worste-case-scenario is a password sync. Rather re-authenticate the caller using a realm which already exist.
Active Directory is not suitable due to the requirement that the non-SAP application must be able to authenticate users if the WAN/LAN is down.
I would consider an application specific password self-service as a failover only and go for the AD or an "identity provider" which your applications trust as a service.
If your AD or entire network goes down you will probably be in bigger trouble than passwords... so you should not expose "raw" passwords during normal operations for this eventuality...
Cheers,
Julius

SAP B1 Client upgrade in Vista Ultimate OS

I am using Vista Ultimate. I am able to install the SAP B1 2005 B client in the Client system. I am unable to upgrade the client. It gives me an error saying that wrong user name or password. I am fully sure that the user name and passwords are right. Please help

Method 1 - When installing from the Client Setup folder in B1-SHR folder
1. After we choose the path to install the SAPB1 client, one window pops up asking the Database server LoginID and password.
2. On giving the correct login credentials, the following error message is given by the system. 'Wrong User Name or Password'
Method 2 - When Installing from the CD
1. The SAP B1 client is getting installed in the Client computer.
2. When connecting to a company after giving the login credentials, the system asks whether to upgrade the client to a higher patch version. On clicking 'OK', then system gives the following error message 'Wrong User Name or Password'
I have installed the same SAP B1 client in the xp computers. Hope I have clearly explained. Thanks

Password of SAP* in Client 100

Similar Messages

Maybe you are looking for