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.

Similar Messages

I can't find any support package for Solution Manager 4.0

I can't find any support package for solution manager at
Support Packages and Patches - > SAP Technology Components
SAP Technology Components
GATEWAY
JAVA LOG VIEWER
SAPCAR
SAP EXCHANGE CONNECTOR
SAP CR CONTENT
SAPROUTER
SAPSECULIB
SAPSSOEXT
I'm searching it at a wrong place?

You´re at the right place - but your user doesn´t seem to have permissions to download them.
You have a license for Solution Manager?
Markus

Error in xpras when importing support packages in solution manager

Hello,
We are importing support packages in our solution manager and we begun
the process more than two weeks ago and the process is still running.
I have stopped the system and restarted the import again, but it seems
to be the same. The SP queue is:
SAPK-1507EINSTPL
SAPK-1507FINSTPL
SAPK-1507GINSTPL
SAPK-1507HINSTPL
SAPK-1507IINSTPL
SAPK-1507JINSTPL
SAPKB70015
SAPKA70015
SAPKITL426
SAPKIPYJ7F
SAPKW70017
SAPKU50012
SAPKB70016
SAPKA70016
SAPKITL427
SAPKIBIIP9
SAPK-40012INCPRXRPM
SAPK-40013INCPRXRPM
SAPK-40014INCPRXRPM
SAPKNA7012
SAPKNA7013
and there is an error (rc=12) at the method execution step in package SAPKU50012 or in SAPKB70016.
Now, there is an rc 12, but the queue is running, the import queue hasn't cancelled, but it seems to do nothing. The RDDEXECL job log is:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server crosol203 were synchronized
Error Building the ENH TreeObject Type:XHObject Name:EH_FJ_FUBA_PARA_VERS
the job was running for 149.332 seconds and at that moment I stopped the sap system. After restating the system I imported the queue again and now, the process has been running for more than 13500 seconds.
We have checked note number 1142410 and all the modifications were already implemented in the system.
Thanks and best regards,
Ana.

Hello Sunny,
The problem is still happening. I have read and apply all the threads you suggested, nut they didn't resolve the problem:
I have updated the kernel
I have checked table DRSEG and it has no problems.
I don't have any syntax errors so I haven't run the SGEN as I think it doesn't apply.
After changing the kernel I have started the sap system and the job rddexecl has started itself before running again the SPAM and reimporting the queue.
I already have 6 support packages without running the method execution step and I don't know how much time it will consume.
Regards,
Ana

Solution Manager 3.2 SP 8- Change Request Management Configuration Problem

Hi friends,
We are in process of implementing SOLMAN 3.2 SP8 in our landscape.I am facing problem in configuring change request management.
When the developer is working on an urgent correction document we are facing a problem.The steps we are following are here under provided.
Step 1 :
Selected Action "In development" - > it created the transport request in the dev system.
Step 2:
Action "Log into System" -> made correction attached to the transport request manually and released the task.
Step 3:
Action "Release transport requests" -> The transport request in the development was released.
Step 4:
Went for action "Pass to correction" -> I am facing exceptions which conveys
Status was reset by system
A condition is not satisfied because of an exceptional situation
Not all transport requests yet released
And we would be thankful if you provide the authorization required for the different roles in the change request management.I have followed the help file of SOLMAN 3.2 and create the users as under
User - Role
SOCM_RQSTR - ZSAP_SOCM_REQUESTER
(Derrived from SAP_SOCM_REQUESTER)
SOCM_DVLPR - ZSAP_SOCM_DEVELOPER
(Derrived from SAP_SOCM_DEVELOPER)
SOCM_CHNGNGR - ZSAP_SOCM_CHANGE_MANAGER
(Derrived from SAP_SOCM_CHANGE_MANAGER)
SOCM_CHNGNGR - ZSAP_SOCM_IT_OPERATOR
(Derrived from SAP_SOCM_IT_OPERATOR)
Even then I am facing problems while developer creating transport requests and while logging into development system.
I tried adding S_RFC,S_RFCACL auth objects to their roles but did not help.
Pl. suggest.
Thanks & Regards
Mrutyunjay
Message was edited by: Mrutyunjay Rao Dora

Hi all,
We are trying to implement the Change Request Management piece in Solution Manager 3.2.
We are facing the following issues which I think relate to the same reason:
1)We have created a Maintenance Project in SOLAR_PROJECT_ADMIN and assigned it a logical component, which consists of our two system landscape (namely DEVàQAS). We have also created the IMG project in the DEV system and have distributed that IMG project to both the Solution manager system and the DEV system. Now we have to make the maintenance cycle and task list for that maintenance project, but as we select the project and click on create project cycle it shows the message "The project is not released. Hence cycle can not be created". It is showing the status of project as locked .How can we open or unlock the project to remove the error?
2) Also after selecting the SMI project when we click on the button CTS status switches or project specific Transport route it responds with the error "Project landscape not configured; set the project status to "open" first ".
3)When we click on synchronize single project it prompts for the login of connected system (Development System) and after login, it gives an error "Warning, problems during synchronization of the system Landscape".
For Error resolution, we have checked the system landscape and it does not give us any errors. We have done that, both from the solution manager by going to the transaction SOLAR_PROJECT_ADMIN --> >system landscape tab>selecting our logical component and doing a check by clicking the "Check system Landscape" button. It returns with "no Errors". We also did a check on the TMS configuration by logging directly on to the TMS domain controller system and checking the Transport routes. We have checked the RFC connections without any errors.
Any help would be greatly appreciated.
Thanks
Abhi

Solution Manager - Can support user user changes manegement ??

Hi All,
In solution manager can change request type as a "New user creation" or "User authorization Change".
So that we can keep track of New user creation or change in authorization that are created in respective R/3 system.
The process flow is same like change management for developement correction or customization correction.
Please give me your comments. It will be very valuable for me.
Thanks in advance.
Ravindra Nikam

As I said, it will depend on the scenarios you will configure.
For the installation, you will not need any. When it comes to the configuration (SOLMAN_SETUP) you'll need the authorizations in SMP for S-User.
You can also check here:
Home - SAP Solution Manager Setup - SCN Wiki
Check the prerequisites at these Guide:
https://service.sap.com/~sapidb/011000358700001119962013E.pdf
https://service.sap.com/~sapidb/011000358700001120342013E.pdf
Regards

Solution manager alerts - receiving after one hour

Hello dear experts,
We have installed solution manager in our landscape and connected to D, Q and P systems.
We are getting alerts for the issues that occur in satellite systems to our email box, but the alerts are coming after exactly one hour after the occurance of the issue.
Ex: If a dump occurs on P system at 02:00PM. I get an alert email at 03:00PM.
Please suggest the place where I need to check and change the time difference.
Also, let me know if you need any more details. Please help me ASAP
Thanking you
Mani

Hi
check SAP system and OS time zones
check program RSCONN01 to run every 5 min
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/sap-mail-with-1-hour-delay-2102706?cv=expanded
hope this will help you
Cheers
dEE

Best way to apply Support Packages to Solution Manager

We have a single instance dual stack for SOLMAN 4 running. I want to apply Suppot packages, I need some suggestion what would be the best way to do this, the way I am thinking to proceed for this is -
1. Do kernel and igs upgrade thru JSPM
2. Apply ABAP Support packages and then,
3. apply JAVA support packages
Is it possible to apply ABAP support packages with JSPM?
Any suggestion would be helpful

Patch your abap stack first then the java...
No, its not possible to pacth abap with JSPM (JAVA Support Package Manager)
Regards
Juan

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

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?

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.

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

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

Blue printing and Test Management in Solution Manager

Hi All,
I have a few questions regarding projects in Solution Manager.
1) We currently have our test cases maintaned in an excel sheet. Is it possible to create same in Solution Manager?
2) Our blueprinting was done outside of Solman. To build the test cases do we have to carry out the blueprinting again? or can we just upload the documents?
This is my first time, therefore am a bit lost in this.
Thanks,
Savindi

Hi,
You can keep your test cases in excel sheets. In Solar02, in the test cases tab you'll be able to upload the test cases in xls format or create it.
Regarding the blueprint, there is no way to upload it or use the generated one. I would recommend you to set your whole project
in solution manager and generate the blueprint again.
Kind regards,
Fabricius

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.

Can I Test the Test Package Created in SolMan Directly from ECC?

Hi,
the test plan and test packages are created in Solution Manager. The Test Packages are comprised of transactions (on ECC).
(The business scenarios and processes are defined in Solar01, ECC is defined as logical component and assigned to every tx, the test case description is uploaded in Solar02,...)
The needed Trusted RFC (to enable the tester to start the tx from within SolMan) is running late, but I can see that STWB_WORK tx is also available in ECC.
Of course - when I open it in ECC (logged on as a test user - defined in test package in SolMan) the test package is empty in ECC.
What kind of connection is there within STWB_WORK in ECC and SolMan?
Can one somehow "transfer" the packages from SM to ECC, so the tester can start to test the transactions from ECC directly?
Is it possible to see the results and status overview in SolMan during and after testing?
Thank you in advance,
cheers,
Nenad

Hi
You getting confused between old ECC test workbench and Solution Manager Test workbench.
Test workbench is present there from r/3 version onwards.
When you are performing testing via solman then you have to use the test packages assign to you in STWB_WORK which has the relevant transaction and doc for you to test
here you upload the test result and update status .Later any PM can generate report for overall testing including entire landscape and not one system.
But remember it has got no connection to ur r/3 workbench
The diff between 2 is...solman test workbench is for entire landscape including BI R/3 ECC any other system ...but in r/3 etc the workbench is alone and obsolete now is used for standalone testing.
Hope it carifies ur doubt completely
Regards
Prakhar

Regenerating test packages in Solution Manager 4.0 after blueprint changes.

Similar Messages

Maybe you are looking for