Solman Clients

Currently we have 000 001 100 clients.
As you know 000 001 are default clients and 100 is a copy from 000 client with SAP_CUST profile.
When i tried to configure SLD , i dont see SLD related user id's SLDAPIUSER and other service users.
I guess users are not copied when we did client copy from 000 client with SAP_CUST profile?
What do we do now ?
1. Delete 100 and start using 001 client as productive client ?
2. Can i transfer only user info by doing client copy from 001 to 100 ?
Please give me some input.Thank you

Hi
if all the user exists in both the clients,It doesnt matter whether you use 000, or 001 as the source client,
if you want to include the users in your copy then please add any one of the down profiles that includes the users in the target
SAP_UCUS, SAP_UCSV, SAP_USER... etc
Jansi

Similar Messages

Solman - Client definition in table T000

Hello,
I got a question from Security officer regarding Solution Manager landscape and the definition of table T000 for the productive client 800. I am telling you that Solman functionality requires in some cases that you leave opened the client 800 to record transport requests for Test Plans and Test Packages (though you don't want to transport anyway, it asks you for a transport request),
Is there a clear definition about what is the correct definition of table T000 for a productive Solution Manager?
I appreciate your answers.
Regards
Esteban

Already SCC4 entry for the client has old Logical system name.
Ex:
Client 500
Logical System : <PRD>CLNT500
I need this to be change to <QAS>CLNT500 after BDLS,but it is not happening after BDLs.
Regards,
Srinivas Chapa.

Solman client copy

Hi,
which profile is recommended for a client copy 001-->xxx
Do I have any benefits with a new client or must I use client 001.
KR....wolfgang

Hi,
I would have sayed RTFM except that just for sure i did this my self and found that there is nothing about client copy any more in the 4.0 documentation. From the
3.2 documentation (see below). I would surely not recomend to use 001 as i production client !
Cheers. And don't forget the points if this answer i use full
Lando
2.2.19 Performing the Client Copy
You use this procedure to perform the client copy, which consists of the following steps:
■ Maintain the client with transaction SCC4
■ Copy the client with local transaction SCCL
■ Copy the log les with transaction SCC3
Procedure
For more detailed information on how to perform the client copy, see the separate documentation in the
SAP Library [page 6] :
Solution Life Cycle Management → Software Change Management → Change and Transport System → Client Copy and Transport
. Note
If you intend to install the SAP Exchange Infrastructure on your SAP Solution Manager system, make
sure that you use the prole SAP_UCSV.
Do not use the prole SAP_CUST as stated in the SAP Library documentation.
For more information see the documentation Installation Guide - SAP Exchange Infrastructure on SAP Service
Marketplace at service.sap.com/instguides → SAP Components → SAP Exchange Infrastructure.

Does two seperate client required if the solman monitors DEV and QAS system

Hi All,
This is our client landscape:
1 Dev-SolMan->For all development and quality systems(ECC 6.0, BI and EP).
1 PRD-SolMan->For all production systems(ECC 6.0, BI and EP).
Note: We have build only DEV-SolMan system as of now and we haven't done any configuration yet like either service desk or ChaRm.
The question is:
Do we need to have two seperate clients in DEV-Solman, one for all development systems and one for all quality systems? or Can we have a single client in DEV-Solman to handle all development and quality systems? What is the SAP recommented approach?
Thanks
Sanjai

Hi,
you even don't need separate Solution Manager systems to monitor DEV / QA and Prod. You could use one SolMan client to monitor and administrate all systems / clients.
Maybe it would be a good idea to create different Solution Landscapes, but this depends on your need.
Separate clients are no good option, because CHARM can only activated in on client. Also if you plan to activate charm, you need a solution that contains all systems in your transport landscape (DEV, QAnad Prod).
Kind Regards,
Holger

BW / SolMan Logical System Change

Hello all, I am having a BW related issue and would really appreciate some advice. I realize some of this is for the solMan forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1.
I am embarrased I missed this section in the master guide the first time around. I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

SolMan / BW Logical System Issue

Hello all, I am having a SolMan/BW related issue and would really appreciate some advice. I realize some of this is for the BW forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1
I am embarrased I missed this section in the master guide the first time around.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.
I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.

SolMan BW Setup: Install Datasource not working - no datasources displayed

Hi there,
I am busy with new SolMan EHP1 SPS6 implementation and doing the Basic Settings > BW Setup in the IMG. The SolMan and BW client is the same (all on SolMan client 700), and I have done the General Settings. Moving to the BW-Based EWA Reporting section > Install Datasource from Business Content I initially got the default BW datasources listed (0SM_SMG_ROOT was not there), so I ran RSA9 to fill the components. Now 0SM_SMG_ROOT is there with 0SM_SMG under it, but there are no datasources beneath it. I have gone to RSA1 numerous times and Activated and Replicated the Source System, but the datasources are still not there.
How can I get them? Anything I did wrong?

Hello Bernardt Nel - Priv
Sorry, but I didn't understand why you're using SPRO => SAP REFERENCE IMG => Basic Settings to perform this configuration if SOLMAN_SETUP execute this configuration correctly without problems.
Did you activate the BI Content using SOLMAN_SETUP ?
In step 7 of Basic Configuration of SOLMAN_SETUP there's an activity that activate the BI Content automatically.

Create new client in Solution Manager?

I finished installing Solution Manager 4.0 sp1 for the first time and have the default clients of 000, 001, and 066. I can log on with the SAP* user. I'm a little confused about the next step. Do I create an addtional client (For example, 100) just like a production or development system to use for users, RFC connections, etc.?
Or do I use one of the default clients?

Hi Carl,
As always... the golden rule applies to SOLMAN as well. Never touch the default clients. Have a client copy and then perfrom all the actions from and ON the Copied client. Get going with SCC4 for a new SOLMAN client :).. atleast thats what we follow here as a practice.
All thebest
Br,
Sri
Award points for helpful answers

Client Settings for SM 4.0

Hi Experts,
Can any one explain the client settings in Single SM land scape.
My solman is prompting for Transport Request while I do some SPRO settings.
What is standard client setting for single solman client.
Thanks
Samba

Hi Kata,
if you only have one SM client, you can change the client settings in SCC4 so as the system will not ask you for transport requests.
nevertheless, depending the number of people involed in working on the seetings of SOLAMN, i would recommend to set up the transport requests, just for the sake of keeping a better control of what is being modified, although these transport requests won´t be transported to any other system and/or client.
In my case, I have only one SOLMAN system, with only one working client. The majority of the SOLMAN customizing has been performed without having to store the information in transport requests although I have in SE06 the system set as modifiable, and in SCC4.
automatic recording of changes for client dependent objects
and "Changes to Repository and cross-client Customizing " option set in Cross-Client Object Changes.
This setting is not prompting for change requests when setting up SMSY (for example), but obligues me to register in transport changes any OSS Note which I have had to apply with SNOTE in order to avoid bugs. And this is very useful, becasue I know exactly how many OSS Notes and which ones I had to apply and when (although I won´t transport it anywhere).
Hope this helps
Antonio

Client Copy Solution Manager Enhacement Package 1

Hello solman experts!
I'm going to install SolMan EHP1 (SPS20). I'm preparing execution plan for installation. Now I have problem in step sequence.
Should I make client copy first and then run tamplates for initial configuration (from SOLMAN_SETUP)?
When I installed PI 7.1 I made client copy before template run (I checked note 1309239). But for SolMan I didn't find any information regarding SolMan client copy and template (and also SOLMAN_SETUP) sequence.
Do you have any ideas?

Make copy before customization

TMW_GET_TARGET_SYSTEMS against /TMWFLOW/TRACK_N107

Dear Experts,
I am testing the Charm configuration for 2 system landscape, both are real but test (if ok then it will be implemented on LIVE).
Everything is OK at SOLAR_PROJECT_ADMIN > System Landscape > Change Requests > Check except i am getting this error @ Check Logical Components:
System cancel RFC destination SM_SOLCLNT000_READ, Call TMW_GET_TARGET_SYSTEMS:
Message no. /TMWFLOW/TRACK_N107
SOL is the SID for solman. I have tested RFC connections using SMSY > Systems > System Name > Server > Clients > Selected Client > Check RFC Destination > everything is OK but with waarnings : [recommended but not essential] Expected system ID (ECC) does not match actual system ID (TSR)
RFC Connections maintained & Tested at DEV Client 000 and 600(customizing) && PRD Client 000 and 600(Production) with SOLMAN Client 000 and 100(Charm Client).
What could be the issue? Please help in this regard.
Thanks in Advance.

I reconfigured the CHARM with 3 system landscape now.
2 real systems, 1=DEV, 2.a=QA, 2.b=PRD, meaning DEV is on different instance but QA & PRD are on same instance with different clients.
Still im stuck here:
System cancel RFC destination SM_SOLCLNT000_READ, Call TMW_GET_TARGET_SYSTEMS:
Message no. /TMWFLOW/TRACK_N107
and another error:
No track for project CH4RM with log. system TRN/600
Message no. /TMWFLOW/CM_CHECK038
Help will be appreciated,
Regards.
Zaman.

Discovery System for Solution Manager

I'm looking for an SAP system I can install or access that has the latest Solution Manager code, with sufficent data so that I can perform practical training exercises. Unfortunately, there's little scope for experimenting with these systems due to the possible impact on production systems and projects, so I don't want to "play" with any of my customers systems except as a last resort.
I'm open to paying for acces, subject to cost and suitability.
PS If that last line (about paid access) contravenes SDN policy, I have no problem wit hsomeone deleting the post and advising me to repost the thread without reference to cmomercial considerations

Hi Sudeep,
As per the Quick guide for V3, to login to Solman Client 001, the user /pw - : sap*/admin123
Since the sap* is locked, login with admin/admin in client 001 and unlock the required user account.
R,
Chaitra

SMSY_SETUP: via SLD: "The SLD server connection is inactive"

Hi folks,
setting up the Solman 4.0 and want to replicate our landscape from our System Landscape Directory.
I followed the instructions in SMSY, set the RFCs etc.
- set the user / pw in SLDAPICUST
- in SMST_SETUP, in the expert settings: put the right user (Administrator), host and port of the SLD
I checked customizing with transaction SLDCHECK ->everything ok, except it's coplanming that it cannot find settings for my Solman-client (yellow).
When triggering the Data transfer via SMSY_SETUP, "SLD", I get in the application log this error message:
"The SLD server connection is inactive", (Message no: SCDT_LIS_IF011)
"Access the SMSY_SETUP transaction to check the connection data for SLD in the expert settings"
Has anybody an idea how to "activate" the SLD server connection?
I cannot find anything what I am missing there...
Thanks
Christian

Hello Christian,
Please check the following document in SAP Service Marketplace. It has been designed to tackle with some of the questions on system data exchange between SAP Solution Manager and SLD, with an overview on all required steps and guides as well as some tips and tricks.
It also contains answers on how to proceed when the SLD Server is inactive:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000538663&_SCENARIO=01100035870000000202&_OBJECT=011000358700000530282007E, see especially chapter 5. Answers to questions 1 and most probably to question 3 (in current document version on slide 7).
I hope this helps to solve your issues.
Best regards,
Doreen

Trusted RFC not working for different user , working for same user

Dear All,
I have two SAP system - One Solman (7.0) and another ECC 6.0 (SR3) on HPUX box with Oracle DB (Unicode).
I want to establish Trust relationship between these system.
I have configured the same, as per the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm
and note 128447.
My requirement is one user X in solman client 001,
will execute some test plan (Tcode stwb_2) which will take the control to ECC 6.0 client 200, execute the tcode as user Y and come back in Solman again.
The user X (SAP_ALL) exists in Solman - client 001 and user Y (SAP_ALL) exists in ECC 6.0 - client 200.
In ECC 6.0 client 200, I have created a role ZRFCACL with the following and assigned to the user Y (as per the above help / note):
Role : ZRFCACL
Auth. Obj: S_RFCACL
Value assigned to fields are:
     RFC_SYSID : SOL
     RFC_CLIENT: 001
     RFC_USER : X
     RFC_EQUSER: N
     RFC_TCODE : *
     RFC_INFO : *
     ACTVT     : 16
Whenever the user X is trying to execute the test from solman, he is getting the error : "No authorization to log on as trusted system (RC = 0)"
Each time the user is trying the above, in ECC 6.0, the following dump is occuring:
CALL_FUNCTION_SINGLE_LOGIN_REJ under username SAPSYS
I have assigned the role ZRFCACL to user X in Solman also.
Next, I have performed the following check:
created one user M in both system
created the role ZRFCACL2 in ECC 6.0 client 200 as follows and assigned the role to user M:
     Role : ZRFCACL2
     Auth. Obj: S_RFCACL
     Value assigned to fields are:
          RFC_SYSID : SOL
          RFC_CLIENT: 001
          RFC_USER : ''
          RFC_EQUSER: Y
          RFC_TCODE : *
          RFC_INFO : *
          ACTVT     : 16
Assigned SAP_ALL to user M in both system (So the user M in Solman does not have ZRFCACL2).
This time, the trust relationship worked and no dump got generated.
I have also checked the thread Trusted RFC do not work
but unable to resolve the issue.
Any suggestion where the things are going wrong in this / what else I need to check or this is not possible at all?
Thanks in advance for your help.
Sudip

Hi Valdecir,
Thanks for the reply. I am providing the detail of the generated dump below:
Please check in case any clue is there.
Runtime Errors         CALL_FUNCTION_SINGLE_LOGIN_REJ
Date and Time          12.08.2008 18:59:32
Short text
No authorization to logon as trusted system (Trusted RC=0).
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPMSSY1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An RFC call (Remote Function Call) was sent with the invalid user ID "98819 "
. Or the calling system is not registered as trusted system in the
target system.
How to correct the error
The error code of the trusted system was 0.
Meaning:
0    Correct logon as trusted system mode
1 No trusted system entry for the calling system "SOL " or the
security key entry for the system "SOL " is invalid
2 User "98819 " does not have RFC authorization (authorization object
(S_RFCACL) for user "98819 " witl client 001.
3    The timestamp of the logon data is invalid
The error code of the SAP logon procedure was 1.
Meaning:
0    Login was correct
1    Wrong password or invalid user ID
2    Locked user
3    Too many attempted logons
5    Error in the authorization buffer (internal error)
6    No external user check
7    Invalid user type
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 0
MM Used. 1194640
MM Free. 2992576
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "489F2BD6C36D0F12E10000000A0A049E"
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "SOL"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 001
User................ 98819
Transaction......... "SMSY"
Call Program........."SAPLSRTT"
Function Module..... "SCCR_GET_RELEASE_NR"
Call Destination.... "SM_RD3CLNT200_TRUSTED"
Source Server....... "gcbsolm_SOL_00"
Source IP Address... "10.10.4.206"
Additional information on RFC logon:
Trusted Relationship "X"
Logon Return Code... 1
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
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 67
of the (Include) program "SAPMSSY1".
Source Code Extract
Line
SourceCde
37
endmodule.
38
39
module %_rfcdia_call output.
40
"Do not display screen !
41
call 'DY_INVISIBLE_SCREEN'.
42
perform remote_function_diacall.
43
endmodule.
44
45
module %_cpic_start.
46
if sy-xprog(4) = '%RFC'.
47
perform remote_function_call using rfctype_external_cpic.
48
else.
49
call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
50
perform cpic_call using convid.
51
endif.
52
endmodule.
53
54
55
form cpic_call using convid type c.
56
communication send id convid buffer header.
57
if sy-subrc eq 0.
58
perform (sy-xform) in program (sy-xprog).
59
else.
60
message a800.
61
endif.
62
endform.
63
64
form remote_function_call using value(type).
65
data rc type i value 0.
66
do.
>>>>>
call 'RfcImport' id 'Type' field type.
68
if sy-xprog = 'JAVA'.
69
system-call plugin
70
id 'JAVA' value 'FORW_JAVA'
71
id 'RC'   value rc.
72
if there is no rollout on the JAVA side which
73
rolls both, JAVA and ABAP, we return to the
74
C-Stack and reach this point
75
76
in case there was an rollout, the ABAP-C stack is lost
77
and we jump direkt to this point
78
79
here we trigger the rollout on this Abap side with
80
the following statement
81
system-call plugin
82
id 'JAVA' value 'ROLL_OUT'
83
id 'RC'   value rc.
84
else.
85
perform (sy-xform) in program (sy-xprog).
86
rsyn >scont sysc 00011111 0.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080812
SY-UZEIT
185932
SY-XPROG
SAPRFCSL
SY-XFORM
READ_SINGLE_LOGIN_DATA
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         SAPMSSY1                            SAPMSSY1                               67
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name REMOTE_FUNCTION_CALL
%_DUMMY$$
0000
0000
2222
0000
SY-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
SYST-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
HEADER
000000000000
000000000000
TYPE
3
0000
0003
SY-XPROG
SAPRFCSL
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5455445422222222222222222222222222222222
3102633C00000000000000000000000000000000
%_ARCHIVE
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RC
0
0000
0000
SY-XFORM
READ_SINGLE_LOGIN_DATA
000000000000000000000000000000
000000000000000000000000000000
544455444445444445445422222222
2514F39E7C5FCF79EF414100000000
%_SPACE
0
0
2
0
No.       1 Ty.          MODULE (PBO)
Name %_RFC_START
%_PRINT
000                                                                                0###
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RFCTYPE_INTERNAL
3
0000
0003
Internal notes
The termination was triggered in function "ab_xsignon"
of the SAP kernel, in line 2491 of the module
"//bas/700_REL/src/krn/rfc/absignon.c#9".
The internal operation just processed is "CALY".
Internal mode was started at 20080812185932.
Calling system.....: "SOL "
Caller.............: "98819 "
Calling client.....: 001
RFC user ID........: "98819 "
RFC client.........: 200
Trusted return code: 0
Logon return code..: 1
Transaction code...: "SMSY "
Active state.......: "-782823270"
Note: At releases < 4.0, the information for the caller is not
available.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x4000000002b43cb0 SignOnDumpInfo + 0x280 at absignon.c:2491 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000002b3f2f0 ab_xsignon + 0xb30 at absignon.c:876 [dw.sapRD3_DVEBMGS00]
(5) 0x4000000002aa4cb0 ab_rfcimport + 0x1ad0 at abrfcfun.c:3599 [dw.sapRD3_DVEBMGS00]
(6) 0x40000000040f4a80 Z8abjcalyv + 0x500 [dw.sapRD3_DVEBMGS00]
(7) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003f538b0 Z9abxeventPKt + 0xb0 at abrunt1.c:281 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003f360a0 ab_dstep + 0x280 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001cb4600 dynpmcal + 0x900 at dymainstp.c:2399 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cab0e0 dynppbo0 + 0x280 at dymainstp.c:540 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fb4de0 TskhLoop + 0x4e20 at thxxhead.c:4518 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(20) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMSSY1
0
11.04.2005
09:27:15
22528
E
1
Prg
SAPLSCCA
1
05.07.2005
13:10:18
52224
E
2
Prg
SAPRFCSL
0
13.02.2005
17:31:45
17408
E
3
Typ
RFCSYSACL
0
13.02.2005
17:31:45
7168
4
Typ
SYST
0
09.09.2004
14:18:12
31744
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program SAPMSSY1
SYST                                       . .       : :     00004612
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
Program SAPRFCSL
RFCSYSACL                                  . .       : :     00001760
SOL                             RD3
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
116
CLEA
00
0035
SAPMSSY1
60
117
CLEA
00
0036
SAPMSSY1
60
118
CLEA
00
0037
SAPMSSY1
60
119
MESS
00
001C
SAPMSSY1
60
120
ENDF
00
0000
SAPMSSY1
62
121
00
0000
SAPMSSY1
62
122
PERP
00
0001
SAPMSSY1
64
123
PERP
02
0000
SAPMSSY1
64
124
WHIL
00
0002
0000
0000
0000
0000
0000
0000
SAPMSSY1
66
128
WHIL
00
0003
0000
0000
0000
0000
0000
0000
SAPMSSY1
66
132
BRAN
05
001E
SAPMSSY1
66
133
CALY
00
0003
0038
002A
0005
002B
0000
0000
SAPMSSY1
67
>>>>>
CALY
02
0000
0039
8000
0000
0000
0000
0000
SAPMSSY1
67
141
COMP
00
0002
0010
003A
SAPMSSY1
68
143
BRAF
02
000E
SAPMSSY1
68
144
SRFC
01
0000
003A
003B
SAPMSSY1
69
146
SRFC
01
0000
003C
C000
SAPMSSY1
69
148
SRFC
02
0000
0000
0000
SAPMSSY1
69
150
SRFC
01
0000
003A
003D
SAPMSSY1
81
152
SRFC
01
0000
003C
C000
SAPMSSY1
81
Thanks & Regards
Sudip

Installing license for solution manager in DS (user/PW : sap*/pass)

Dear Experts,
I need to install license for the solution manager in the Discovery system 3.
I made 3 mistakes while logging in, so, the user/PW : sap*/pass can't logon to the system.
Can you please help me find how to log on to the client 001 of the solution manager when the user: sap* and PW : pass is unable to log on?
Thanks
Regards,
Sudeep

Hi Sudeep,
As per the Quick guide for V3, to login to Solman Client 001, the user /pw - : sap*/admin123
Since the sap* is locked, login with admin/admin in client 001 and unlock the required user account.
R,
Chaitra

Solman Clients

Similar Messages

Maybe you are looking for