Test cases in Solution manager

I have uploaded two test case documents under 'Test case' tab for a Business Process in the transaction solar02.
But those two test documents does not appear in STWB_WORK for that Business Scenario.
Any advices?

Hi,
Perhaps this might be of interest to you, if it happens that inconsistency is affecting the availability of your test documents
You can use the program as it does not do any harm to
your projects (it does not delete anything, it add only some entries
to a table, if at any circumstances they are missing)
The use of the program is quite simple.
Start transaction SE38 and enter the program GHE_CHECK_TTREEI_ENTRIES
and hit execute (F8).
In the next screen enter the project you would like to check using the
F4-help.
There is also a field TEST. When you enter here 'X' then no modification
will be done, but only the check whether there are entries missing
is performed.
If the program finds any missing entries, simply re-run the program
without the 'X' at field TEST and the program corrects the inconsistency
Hope this helps.
Cheers
SH

Similar Messages

Regenerating test packages in Solution Manager 4.0 after blueprint changes.

Hello,
This is the scenario.
A test plan and test package (1 process = 1 test package) have been created.
The blueprint has changed and a new step has been added to the process (the process that has already been assigned into a test package.
How do you get that new task/step into the test package??
Current situation:
I've managed to regenerate the test plan with the new task listed under the process. However when I go into change test package the new process is NOT there. Why is that? Can I had a new step to a package or not?
Regards
Dan

You must go down to the transaction leveland click and then regenerate it will then be eligible in the package for regeneration.

Automating uploading of test case through SOLAR02 - Solution Manager

Hi
Currently our client is uploading hundreds of test cases into SOLUTION MANAGER manually, they have lots of test cases to be uploaded, and doing it manual is a tedious process.
Client is requesting us to develop a program which will automate the feature of uploading the test cases into SOLUTION MANAGER.
Detailed requirements :
Client needs a Program to be developed in such a that, client will provide 'Project name', 'Business Scenarios' and the 'Business Process'. Also provides the folder on the desktop system with the test case file.
Once user make this selection it(program to be developed) should upload the test document (XLS File) will be saved under a particular folder and also the manual steps maintained in the test case get uploaded.
To meet the above requirement we are in process of debugging (tcode: SOLAR02) to check if there is any function modules or BAPI to upload the test documents and the respective test cased to develop this program, but we could not make any progress.
Any help in this regard is highly appreciated.
Many Many Thanks in advacne.
Ramesh.

Hello,
we had this need a year ago and got the answer that it's not possible to upload several documents at one time automaticly.
There should be a SAP partner offering a solution for it, but he could only offer it for a totaly new Solution Manager environment and not for a database which has already content in it.
Sorry, we would also be happy to have an automated solution.
Sonja

Connection between Solution Manager Testing und Test Workbench

Hello,
I have Problems understanding the connection between the test organization in the solution manager and the test workbench in the corresponding sap system.
The documentation says that the Solution Manager reuses the test workbench functionality. It is not clear for me how this connection works. In the solution manager you define test cases in the configuration of the project. When you create a test plan in the solution manager you can use the testcases of the project. But when you execute the testcases you do it in the corresponding sap system where the transaction of the test case is. Does this mean that the test cases und test plans that you create in the solution manager are transported to the target sap system? If this is true, when is the transport taking place?
Thanks a lot!
Regards, Lars.

Hi Lars,
I think you are confused with solution manager and tools like QTP.
The difference between solution manager and QTP/ECATTT is the eCATT or QTP are used for creating the test scripts or the test cases but solution manager is used for storing all types scripts centrally.
It means say you have manual test scripts eCATT and Ext QTP scripts lying on the R/3 servers but from solution manager you can create a project comprises of all the scenario and linked test cases of various type.
Now at a later time when you start testing a manager login to solution manager enter the test plan project name etc and can check what is the current status of the test
1. how much testing is completed
2. Who is the tester what is the test script where or on which testing took place etc
you can check my weblog to knw how to manage and perform testing via solution manager.
/people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager
Please reward points for the same.

ECatt testing through Solution Manager

Hi,
Could anyone please send me the documents for creation of test cases through solution manager?
My email id is: [email protected]
Regards
Karan

Karan,
Did you not check the first thread on the forum; I am a bit unclear if your query is something that the thread did not deal with OR it's just that you haven't read the thread so far.
eCATT Articles On SAP SDN - Series Of 8 Weblogs
Regards,
Srini

Weighting of test cases

Hello,
Does anybody know how to use weighting of test cases in Solution Manager?
In the Central Test Workbench settings (Transaction STWB_SET ) its an option called "Weighting of Test Cases" We would like to use this functionality, but can't figure out how to use it.
Does anybody know?
Even better, does it exist any description?
Br
Are H Vestrum
Edited by: Are H Vestrum on Jun 16, 2008 2:07 PM

Hi Are,
F1 Value help shows for a new entry:
Profile Weighting Test Status
Profile
Profiles, which are later put in the test plan attributes, are specified in the transaction STWB_SET. They are a prerequisite for putting the weighting and test plan consistency settings under an attribute.
Weighting
To be able to weight a test case in a test plan, a factor is assigned to a test case priority in the transaction STWB_SET. This visualizes the relevance of a test case in a test plan, in the status analysis.
Test plan consistency
The test plan consistency is an analysis of the dependency between a test case status and it messages, according to the message attributes Priority and Status. The test plan consistency settings are also made in the transaction STWB_SET.
Weighting allows value from 1-9.
Greetings from Walldorf,
Ruediger

Solution Manager-Test Plan Management_Issues

Dear Friends,
I am working on Solution Manager 4.0--Patch level:12
Highest support package level:SAPKITL422.
Before uploading the patch level 12, if i enter into t.code SOLAR01 / SOLAR02,
i can only raise support message by choosing the tab "Messages"
I CAN NOT raise an "Issue" at that time. (Before uploading patch level:12)
Now i have uploaded the patch to 12.
Now i can raise support message as well as an issue in both t.codes (SOLAR01/SOALR02).
My problem is:
Now i want to track an issue related to my integration testing/ UAT through solution manager.
If i enter into t.code STWB_WORK, i can only raise a support message. But i can not raise an "Issue" in STWB_WORK.
How to activate an "Issue" also in STWB_WORK?
Any other patch level has to be uploaded to activate?
regards
Senthil

By the way:
What's the difference between a Support Messages and an Issue?

Importing existing test cases with multiple test steps into e-Manager

When I import my excel-based test cases into e-Manager Enterprise, each test step appears as a separate test case. How can I correct this problem?

Please try attached XLS. You need to blank out every column except for the test steps column for rows which are your test steps.

Setting up EarlyWatch in Solution manager

Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1.     Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2.     Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3.     Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4.     Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5.     This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6.     I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors         SYNTAX_ERROR
Date and Time          24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RDSVASAEW_ROOT_____________073
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr           = po_ctnode->versnr.
2117
ls_stdparameter-grp              = po_ctnode->grp.
2118
ls_stdparameter-id               = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp    = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id     = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp              = pf_grp.
2124
ls_stdparameter-versnr           = pf_versnr.
2125
ls_stdparameter-reference_grp    = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at    actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event     = pf_event               ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number    = ls_actrel-action
2140
importing
2141
pf_form_name      = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod.                    "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event     ne space                 )
2157
or   exec_time = gf_exec_time_1
2158
or   exec_time = gf_exec_time_2
2159
or   exec_time = gf_exec_time_3
2160
or   exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
11 FORM         SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2146
EXECUTE
10 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       2025
LCL_SESSION=>EXECUTE
5 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1995
LCL_SESSION=>EXECUTE
3 FUNCTION     SAPLDSVAS_PROC                      LDSVAS_PROCU02                        303
DSVAS_PROC_SESSION_OPEN
2 METHOD       CL_DSMOP_SOLUTION=============CP    CL_DSMOP_SOLUTION=============CM01P   184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT        RDSMOPBACK_AUTOSESSIONS             RDSMOPBACK_AUTOSESSIONS                72
START-OF-SELECTION
Chosen variables
Name
Val.
No.      11 Ty.          FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION                                           00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.      10 Ty.          METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION                                           00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000                                  ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store        = 0x807E0D3E |
| ext1         = 0x00000000 |
| shmId        = 0     (0x00000000) |
| id           = 1911 (0x77070000) |
| label        = 3668 (0x540E0000) |
| fill         = 1     (0x01000000) |
| leng         = 44    (0x2C000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000007 |
| occu         = 16    (0x10000000) |
| access       = 4     (ItAccessHashed) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 1     (ItUnique) |
| keyKind      = 3     (user defined) |
| cmpMode      = 8     (cmpManyEq) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0xC0AB0D3E |
| pgHook       = 0x00000000 |
| idxPtr       = 0x78F10D3E |
| shmTabhSet   = 0x00000000 |
| id           = 2504 (0xC8090000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 16    (0x10000000) |
| lineAlloc    = 16    (0x10000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = Not allocated |
| collHook     = Not allocated |
| ext2         = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No.       8 Ty.          METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.       7 Ty.          METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store        = 0x68550D3E
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 1919 (0x7F070000)
label        = 3674 (0x5A0E0000)
fill         = 26    (0x1A000000)
leng         = 8     (0x08000000)
loop         = 384   (0x80010000)
xtyp         = TYPE#000029
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 4     (cmpSingleEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xB0B10D3E
pgHook       = 0xF0882E3E
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 2508 (0xCC090000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 48    (0x30000000)
lineAlloc    = 48    (0x30000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No.       6 Ty.          METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No.       5 Ty.          METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store        = 0x90C50D3E |
| ext1         = 0x30F3DE3D |
| shmId        = 0     (0x00000000) |
| id           = 1920 (0x80070000) |
| label        = 3670 (0x560E0000) |
| fill         = 1     (0x01000000) |
| leng         = 100   (0x64000000) |
| loop         = 264   (0x08010000) |
| xtyp         = TYPE#000094 |
| occu         = 1     (0x01000000) |
| access       = 1     (ItAccessStandard) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 2     (ItUniqueNon) |
| keyKind      = 1     (default) |
| cmpMode      = 2     (cmpSingleMcmpR) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0x08AB0D3E |
| pgHook       = 0x00000000 |
| idxPtr       = 0x00000000 |
| shmTabhSet   = 0x00000000 |
| id           = 2505 (0xC9090000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 1     (0x01000000) |
| lineAlloc    = 1     (0x01000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = 0xB0F0BE3D |
| collHook     = 0x00000000 |
| ext2         = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No.       4 Ty.          METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No.       3 Ty.          FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USER

Please replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur.

Working on Solution Manager

Hi Gurus,
in our project we are having to work through solution Manager. I am new to the solution Manager environment.
a) Is there any link that helps us understand the basics of working on solution manager.
b) Also, i understand we need to give the transaction codes that we work on in solution manager. (But in HCM as we work in the IMG the transaction code is always seen as SPRO for most of the configuration)
c) How do we set the T Codes for entire configuration?
We have the sub modules
a) Personnel Administration (Recruitment Included)
b) Organisation Management
c) Time Management
d) Payroll
e) Personnel Development (PMS- OSA)
f) Training and event Management
g) ESS and MSS
Awaiting your reply and Thanks in advance
Regards
RR

The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
The concept is very user friendly and can be easily worked on. Thank you friend for your response.
i used solar 2 and was able to work further.
Regards
RR

Regarding Monitoring Service for Solution manager

We need to configure "Monitoring" services in SAP solution manager 7.0.
Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
How many Minimum servers required to configure Monitoring services in solution manager system.
Also if any good document reference for this?
Thanks

Hi Jai,
welcome to sdn.
COMPONENTS & TOOLS OF SAP NETWEAVER
SAP Solution Manager
The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
As part of SAP Solution Management Solutions, the customers receive best practices relating to:
- Global Strategy and Service Level Management
- Business Process Management
- Management of MySAP Technology
- Software Change Management
- Support Desk Management
SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
- Manages the technical risk associated with the implementation of the solution ensuring technical robustness
- Helps leverage users core competencies in implementing solutions
- Ensures solution works as intended with best practices built in.
see these links...
http://www.ne-sap-solution-manager.com/
http://www.saptechies.com/category/sap-solution-manager/
thanks
karthik
reward me if usefull

SAP Solution Manager SR1 with MSSQL on W2K3 IA32 - Problem with Kernel

Hello,
we are implementing a sandbox in order to test the SAP Solution Manager 4.0 SR1 with MSSQL on W2K3 IA32. Therefore we ordered the installation CD for the above mentioned configuration. Instead of getting the SAP NETWEAVER Kernel SR1 we got SR2. Now we have the problem, that the installation program SAPINST is requesting the SR1- Kernel.
Unforunately the SR1-Kernel seems no longer available in the download section.
It would be fine to get a suggestion how to solve the problem.
Thanks
Best regards
Ralf Richter ([email protected])

Hi Andreas,
thanks for the hint, I have already checked the LABEL.ASC. I have no LABEL.ASC-Key for the SAP Netweaver 2004s SR1, so it would be a possibilty to substitue this key. But neverhteless, I think, there should be another official procedure in order to use the SR2 instead of the old SR1. I have contacted Klaus Billing at SAP as recommended in the OSS Note 918078. Best regards. Ralf R.

User Manual for Solution Manager

Friends,
For a first time user of Solution Manager, is there documentation available to guide one through the rigour? Maybe a user manual on how to effectively harness Solution Manager during the project implementation cycle.
Thanks and Regards,
Sameer Aroskar

you can also check this
<a href="/people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager and Perform Testing using Solution Manager</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce0b74e3-0601-0010-29a0-f2a6af98ef06">How SAP Solution Manager Can Smooth Your Next Upgrade Project</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2a92c290-0201-0010-4b8f-a2aaaa3b822e">SAP Solution Manager - Test Drive SAP Solution Manager in an Implementation Project</a>
I hope these will be fine for now
Regards
Milton

EHP4 solution manager xml file not supporting

Hi Support Team,
Here we are in middle of installing ehp4 installtion struck with an
error : "Error reading stack info . freturn code=-1,Reason = "the stack
configuration is not valid for the system HDC,inst no. 0020592069."
Here our HDC is ERP system where the EHP4 installation is
undergoing.Please find the screenshot attached.
SApehpiconsole log : (last 200 lines)
A trouble ticket and an archive with all relevant log files have been
generated.
Trouble ticket: "/oracle/EHPI/abap/log/SAPehpi_troubleticket.log"
Log archive: "/oracle/EHPI/abap/log/SAPehpi_troubleticket_logs.sar"
01) * Repeat phase SPAM_CHK_INI to continue at the point it stopped
02) - Restart the current module from the beginning
03) - Exit this program
Choose action: Repeat phase SPAM_CHK_INI to continue at the point it stopped
>> 2010/03/15 11:45:53 START OF PHASE PREP_CONFIGURATION/SPAM_CHK_INI
>> 2010/03/15 11:45:56 END OF PHASE   PREP_CONFIGURATION/SPAM_CHK_INI
>> 2010/03/15 11:45:56 START OF PHASE PREP_CONFIGURATION/RUN_RSUPGSLI
Starting of Configure selective-language-import option in batch (job RSUPGSLI)
working ...
>> 2010/03/15 11:46:00 END OF PHASE   PREP_CONFIGURATION/RUN_RSUPGSLI
Execution of PREPARE module "Configuration and language selection" ends at 20100315114600
Execution of PREPARE module "Extension module for start release >= 40B" begins at 20100315114600
>> 2010/03/15 11:46:00 START OF PHASE PREP_EXTENSION/UPLOAD_REQUEST
Uploading data ...
>> 2010/03/15 11:46:07 END OF PHASE   PREP_EXTENSION/UPLOAD_REQUEST
>> 2010/03/15 11:46:07 START OF PHASE PREP_EXTENSION/SELSTACKXML
>>>> Stack configuration <<<<
Please specify a valid Enhancement Package stack configuration. The ADD-ON and
Support Package selection in the BIND_PATCH phase is taken from there. For
more information, see SAP Note 1022704 .
You need to include an Enhancement Package into the procedure. Please refer to
the manual for further information.
01) * Provide stack configuration file in input field below
Select configuration:: Provide stack configuration file in input field below
STACKFILE: /sapcd/SMSDXML_HDC_20100308092914.238.xml
>>>> Stack configuration <<<<
Please specify a valid Enhancement Package stack configuration. The ADD-ON and
Support Package selection in the BIND_PATCH phase is taken from there. For
more information, see SAP Note 1022704 .
You need to include an Enhancement Package into the procedure. Please refer to
the manual for further information.
01) * Provide stack configuration file in input field below
Select configuration:: Provide stack configuration file in input field below
STACKFILE: /sapcd/SMSDXML_HDC_20100308092914.238.xml
>>>> Stack configuration <<<<
Please specify a valid Enhancement Package stack configuration. The ADD-ON and
Support Package selection in the BIND_PATCH phase is taken from there. For
more information, see SAP Note 1022704 .
You need to include an Enhancement Package into the procedure. Please refer to
the manual for further information.
01) * Provide stack configuration file in input field below
Select configuration:: Provide stack configuration file in input field below
STACKFILE: /opt/SMSDXML_HDC_20100315065507.342.xml
Please guide us accordingly.
Regards
sap123

Hi Gurus
I am facing the same issue in configuration phase.
The error is "Error reading stack info.
       Return Code = -1, Reason = "No vendor specified"
Our Solution manager is on EHP1 now and we are facing this error after ehp1 upgrade, earlier we did one ehp4 upgrade test successfully with solution manager 7.0 before. But after upgrading solution manager to EHP1 we are facing this issue.
Can anyone help me on this....
Waiting for your response.
Thanks
Khalid

Solution manager and BW

Does anybody know something about using BW 3.5 (CRM content) for reporting data from Solution Manager, in particular from Support Desk?
Standard report CRM_DNO_SERVICE_MONITOR does not fit our needs in SLA reporting.
We need some more "powerful" reporting,so we would like to check CRM business content in BW. But, so far,without significant results.
Thanks in advance to everybody.

Hello Michele,
you might have a look at SolMan 4.0, for example on http://service.sap.com/solutionmanager -> media library -> Use Cases -> SAP Solution Manager Reporting, page 33 or 46. May be it's easier to upgrade to SolMan 4.0 than to implement the same on SolMan 3.20.
Bye

Test cases in Solution manager

Similar Messages

Maybe you are looking for