Charm and Test workbench

We are using charm and would like it to link together with the test
workbench? In this way we will be able to use are test cases for the
defined processes in the testing in charm.
Does SAP have plans to link test workbench to charm?

Hi Yosh,
I know a very famous pharma company where ChaRM has been implemented successfully. Due to some restrictions, I am not disclosing the name.
Regards,
Sneha.

Similar Messages

ChaRM and Test Workbench Successful Implementations

Where has ChaRM and/or Test Workbench has been successfully implemented within one of the following industries:
Medical Devices
Healthcare
Pharma
THANKS MUCH!

Hi Yosh,
I know a very famous pharma company where ChaRM has been implemented successfully. Due to some restrictions, I am not disclosing the name.
Regards,
Sneha.

Change Management and Test Workbench for documentation

Hi,
I would like some clarification on the association between change requests and test workbench.
I'm going through scenarios such as creating a maintenance project, creating a task list and service message and then creating a transport request.
During these steps, I want to document the test results prior to migrating these transports into the production system.
My questions are - how do you link the maintenance project and also urgent corrections to a test procedure and documentation. It appears that by using solar01/solar02 and stwb_2/stwb_work, these tests are linked to a project and not necessarily a "change request"
I greatly appreciate if you can elaborate the association between the various areas a bit clearer for me.
Thanks!!!

You need to look for information on usage type "DI", "Development Infrastructure" or "NWDI" (all common abbreviations for the same thing). There were some very good presentations on NWDI at TechEd this year.
Here are some links to help documentation:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/63/7a4d40eae76f13e10000000a1550b0/frameset.htm">Administration of the Development Infrastructure</a>
<a href="http://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/developersguide">SDN NetWeaver Developers Guide</a>
Rich

ChaRM and test management in implementation projects

Hi
I am doing implementation projects in solution manager. i have activated charm in the project so as to transport all the changes related to the project with the project lifecycle.
I have got confusions regarding CHarm and Test MAnagement.. when we activated CHaRM the tester can logon to the system and perform testing and pass the Change Document to the next phase.
What is the standard flow when both CHaRM and TEst Management for a project exists??
Thanks

Please can someone tell me how to use TEST MANAGEMENT and ChaRM for Implementation Project together??
Edited by: Hasan Sidra on Jan 2, 2012 11:11 AM
Edited by: Hasan Sidra on Jan 2, 2012 11:11 AM

Integration of Charm and test work bench or customizing

Hello,
Solution Manager allows one to define the business processes. One can then define test cases for these business processes. Then one can use the test workbench to do the testing.
Is there any way to link the test workbench with Charm?
Are there any such plans for such integration?
Customizing can also be done from the business process definitions in a project. Are there any way that charm can be integrated to make changes in this way?
Regards,
Avrohom Weissman

This is very far from the type of integration I expect to see. Proper incident management means when a problem occurs and incident is logged into the sap service desk. If this incident requires a change it should be forwarded to the CHange Reqest Management (CHaRM). From there it should have a business impact analysis, then a system or architecture review, only then if it is approved should development be started, after the development, it goes into QA for testing. Since the business process is defined in the solman and there are test cases for this business process. It makes sense that one can use the test workbench to verify the business process, and document the testing. If there is a problem with the testing and it needs to go back to development, it should be connected to the same incident logged initially. There should not be a second problem logged. It is still part of the same incident and should be managed as such.
This question exists also for a maintenance project. Once I have an operational system and all the business process defined in the project and a change arrives into ChaRM, why canu2019t the change be done in the project like and implementation?
How can one find out the direction of this product? Does SAP have any plans to develop solman into an integrated tool or will it remain a bunch of simple tools that co-exist on the same server?

E-CATT documentation and I-Tutors for Test Workbench in SOLMAN

Hi!
I looking for suitable documentation for e-CATT (e.g. how to build and integrate automatic e-CATT scenarios).
I need this functionality in connection with SAP Solution Manager's Test Workbench.
Any helpful information will be appreciated.
Thank you!
regards
Thom

Hi,
Please follow my and sapna blogs which will help you to integrate ECATT scripts with solman.
creating ecatt scripts -series by sapna
eCATT Articles On SAP SDN - Series Of 8 Weblogs
Migrating catt to ecatt
/people/community.user/blog/2007/02/05/create-and-migrate-catt-to-ecatt-part-1
Perform Testing with Solution manager
/people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager
Go through above blogs which will show how to integrate any script with solman and generate test plans to manage testing.
Please reward points for thes same.

Difference between Test workbench and HP Quality center

Hello,
What is the difference between SAP test Workbench and the HP Quality center? what is the advantage and disadvantage of each tool?
Thanks in advance
Hassan

the error is in Solution Manager. I am defining the communication parameters in SOLAR_PROJECT_ADMIN / <selected project> / edit / Connection to HP Quality Center. I choose the corresponding project in Quality Center, but when I validate the screen, I get the error I mentioned before, even though the communication user exists in HPQC and is assigned to that specific project.
Thanks for your reply.
Marco

Compensation Workbench Setup and Test Script document....

Hi,
Does anyone out there has setup and test script document for Compensation Workbench that you are willing to share?
Thanks

Hi,
For single system landscape..
Go 000, DDIC ... STMS--> here it will ask for domain controller -- give self domain ---> Domain controller has been assigned .
Now again goto STMS> System overview>SAP SYSTEM >Create ->Virtual system- give name V<SID>
till this point your domain controller is created and virtual system is created .Next our aim is to setup STMS
again goto STMS>transport routes> change > configuration>statndard configuration ---> select second option (development and productino System ) because here your dev system will your own system and virtual system would be production system .
---> pop up will come -> give DEV - SID and Productino SID- it willl automatically create the route .
Save this and exit.
This way We can set single system landscape.
Thanks and Regards,
Arun Rathour

CHARM: Developer and Tester same USER in normal correction

Hi Expert,
i'd like to know if in a normal correction it is possible that Developer and Tester are the same persone.
So the same user have to confirm development and confirm sucessful test.
Now if i try to use the same user i've an error.
Can you help me ??
thanks
Francesca

SPRO
search for Make Settings to Change Transaction Types, and select that activity.
Highlight SDMJ, select the Use Partner Functions folder on the left
in the table on the right:
The first column in the table is the status
The second column in the table is the partner function that the current business partner will be assigned to when save is clicked and the status becomes the first column.
The third column in the table is used for determining if partner functionsu2019 business partners are the same when the document is saved and the status becomes the first column. For example, the Tester (SDCD0002) equals the Developer (SDCD0001) when the status is Confirmed (E0009).
Delete the value in the third column to stop the comparison.

Integration of CHARM and Document Management

Dear All
After a lot of time on sdn wiki and thanks to the key blogging contributors , I now have a decent understanding of how to configure CHARM
To go into more details, i would like to integrate CHARM with the Document Management within Solution MAnager
Would i be right to assume that this integration is currently today in use only by a few GXP kind of customers
But it seems the configuration of document management itself is not so difficult (eg creating document types, statuses, status schemes, signature strategy etc) The IMG has the steps described though in not great detail. Some topics are still bit specialized eg document versioning etc
I was wondering if someone who has already spent time in this area could write a SDN blog or SAP experts coudl write a wiki section
I see this as the next big improvement since everything would be out of the box and external document databases can be discarded etc
Also the workflow of informing and signing documents for clear visibility is on the same system etc
Some requirements could be
1) what could be the minimal document workflow
2) what kind of checks can be implemnet to prevent CD to move forward if a document is not in 'Approved' status
3) at what point could a QM come into picture
etc
Though the documentation is in bits and pieces, if we could have alll at one place - lets say how its done , would be very helpful
Like a Wiki or the SAP CHARM configuration guide
or like the ITSM book by Nathan Williams with illustrations :-)
Thx
Chandrakanth

This is very far from the type of integration I expect to see. Proper incident management means when a problem occurs and incident is logged into the sap service desk. If this incident requires a change it should be forwarded to the CHange Reqest Management (CHaRM). From there it should have a business impact analysis, then a system or architecture review, only then if it is approved should development be started, after the development, it goes into QA for testing. Since the business process is defined in the solman and there are test cases for this business process. It makes sense that one can use the test workbench to verify the business process, and document the testing. If there is a problem with the testing and it needs to go back to development, it should be connected to the same incident logged initially. There should not be a second problem logged. It is still part of the same incident and should be managed as such.
This question exists also for a maintenance project. Once I have an operational system and all the business process defined in the project and a change arrives into ChaRM, why canu2019t the change be done in the project like and implementation?
How can one find out the direction of this product? Does SAP have any plans to develop solman into an integrated tool or will it remain a bunch of simple tools that co-exist on the same server?

ChaRm and CTS+ configuration

Hello Experts,
Can anyone forward ChaRm and CTS+ configuration document to me, I have received Business requirments and trying to configure the same. I would appreciate step by step configuration guide for both.
Thanks in advance.
Regards,
Swapnil Lakhe
lakhess<at>gmail

Hi,
Please find the below steps for Charm confirguration :
1.SAP Solution Manager Implementation Guide  SAP Solution Manager  Basic Settings  SAP Solution Manager System  Activate Integration with Change Request Management
Click on the Execute icon with the text Activate Integration with Change Request Management
Double click the Activate Change Request Management and set up client
It will show the following window type your Change Request Management Client Number
Click on the Integration Solution Manager
If you have different system for Change Request Management gives the RFC destination for that System.
Click back button
Double click on the Integration Change Request Management
You have to maintain the following data here
Column 1: Application: CHARM
Column 2: + : W
Column 3: RFC Destination: NONE
Column 4: + : CUST620
Column 5: + : 1.0
2.SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Standard Configuration 
General activities
Click on the Execute button with the text u201CActivate BC Sets u201C
It will take us to SCPR20 Transaction which is used to Activate the BC sets
Select the BC set SOLMAN40_CHARM_BASICFUNC_001 , it is for solution manager version 4.0
Click on the Activate Button
Create a Request for Activating the BC Set
Click Save button to assign with a TP .Other wise Create a new Transport Request (TP).
In Overwrite Data Box, select the Overwrite data, and in Activation Mode box select Expert Mode Option , Click on OK Button to activate this BC set.
3.SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Standard Configuration 
Transport Management System.
In Order to do all the Settings under the Transport Management System do follow the steps.
All the below settings has to be done in satellite system not solution manager
1.     Define Transport Routes for System Landscape
Go to Transaction STMS
Choose Overview -> Systems.
Double-click each system.
The Display TMS Configuration: System <system ID> screen appears.
Select the Transport Tool tab page.
If the entry CTC does not appear in the Parameters column, enter it there, and then in the Value column, enter 1.
Save your entries.
Configure Transport Strategy
Go to Stms Transaction
Go to Menu Overview  Transport Route
Doubt click on Each System . In the Transport strategy group box, select Single transports
(since only Import Single and Import Project All are used).
In the Quality assurance group box, deselect Delivery after confirmation
1.     Choose Continue.
Activate TMS Trusted Services
Choose Overview -> Systems.
Choose Goto -> Transport domain.
In Management Tab
In Security Options group box
Click on Trusted Services Active
Go to QA Approval Procedure
You should not assign any QA approval system there
Save your Entries
Call Transaction STMS.
Choose Overview  Systems. The system overview appears.
Choose SAP System  Create  Domain link.
The dialog box Request for Linking 2 Domains appears.
Enter the system name, host name and system number of the domain controller you want to link to, and then confirm your entries.
Your SAP System performs the following actions automatically:
o     Generates the required RFC destinations.
o     Sends the address data of the controller to the controller in the other domain.
You can now see that you have requested the domain link to the other domain in the system overview.
Click the Distribute and Activate TMS Configuration ICON on the Application Toolbar
After that Go to SAP System  Check  Connection Test, transport directory and transport tool
Check all once whether it is having inconsistency.
4.Check Configuration of Transport Domain
Log on to every domain controller that is connected to your transport landscape.
Call transaction STMS
Apart from the information "You are logged onto the domain controller", you should not be able to see other messages or warnings.
Generate RFC Destinations to Client 000
Call Transaction SMSY.
Go To Landscape Components
Go to your Satellite System
Click on the Domain Controller System
In the Right side Tab strip, Click on the Clients, Select 000 client Click on RFC generate Button
Give the User name for Read Access and Change Manager
Click the OK Button to Continue
Add Import Authorization to Operator/Administrator
Make sure that the operator and administrator users in client 000 of the target systems have the same name as their user in the Solution Manager   system.
Assign import authorization to the operator and administrator users in client 000 of the target systems (SAP_CHANGEMAN_OPERATOR and SAP_CHANGEMAN_ADMIN roles).
5.Set Project Assignment of Requests as Mandatory
If you want to enable your change request project is mandatory while creating a request for workbench or customization object, follow the steps
Go to Transaction
/N/TMWFLOW/CMSCONF
Select the Change Request Management System
Double click on the Project Assignment column
A new windows opened as follows
In the Attribute Required for Requests Box , Select Mandatory on the Default for all clients List
In the Client u2013Specific Setting Activate the tick mark of the Right side of the Table Control
6.Change Transport Request Option
Requirements
u2022     Repository changes are permitted in the system where you want to change the transport request option. (If they are not, proceed as described in SAP Note 327351.)
u2022     You do NOT use template projects.
Go to Transaction SE38
Enter the following Program   SAPLSCMA
Click on the Display Button
Click the Find icon and type the following keyword,
G_ACTIVATE_CORRECTION_SYSTEM
Click on the OK Button to search
Using Modification, Edit the Program in Change Mode
Delete the following lines ,
message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
And Insert the following lines ,
no_automatic_recording = 'X'.
Call Transaction SCC4
Select the Change Request Management Client and Click the Display ICON.
Go to Transaction SE 11
Enter the table SCMATREED
Choose Display
In Menu Click on Goto -> Indexes,
Choose Yes in the dialog box, and enter the index name 001, and the following short description: Index for Node in SCMATREE.
Maintain Number Ranges
Go to Transaction SNRO
Enter Object Name /tmwflow/M
Click on Number Range Button on the Application Toolbar
Click on the Change Intervals Button
For the new interval, enter 01, and use the F4 Help function to select a value for the From Number field.
The system returns 000000001 to 999999999.
Save the Entries
Come to the SNRO First Screen again; follow the same procedure for the following objects
/tmwflow/d and /tmwflow/v.
SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Extended Configuration  Schedule Manager
( Note in HLL We have using the Standard SAP Variants )
Create Customer-Specific Variant for Task Lists
Click on the Execute button
To Create a New Entries, Click on the Create New Entries Button
Type the Variant Name in the Variant Column Starts with the name space of u2018Zu2019, and in the Description Column you can maintain the description
Define Additional Tasks for Task Lists
Create Customer-Specific Header and Footer Tasks
Install Template Report
For all the above Refer IMG Node, follow the Steps
SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Change Transaction
Check Installation Activities
Make sure that you have performed the iBase IMG acitivities before you proceed with the Change Transaction IMG activities: SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> Service Desk -> iBase.
Check the all the following settings has been done .
Initially Create and Assign the Component Systems as iBase Components
Manually Create and Assign the Component Systems as iBase Components
Assign Business Partners to iBase Components
In the following Link all the Settings comes with BC Set.
SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Change Transaction
USER Authorization
Administrator
SAP_CM_SMAN_ADMINISTRATOR
Change Manager
SAP_CM_SMAN_CHANGE_MANAGER
IT Operator
SAP_CM_SMAN_OPERATOR
Developer
SAP_SOCM_DEVELOPER
Regards
Sreedhar Reddy.A

Email setup for Test Workbench

Hi
I am looking to setup Email notifications for Test Workbench.
Such as, automatically emailing testers when Test packages are assigned
Emailing Developers when a Test Problem Report is created.
How do i do this? Does anyone have any documentation they can share?
Really need some help.
Many thanks

Yes Ramesh,
By setting up ChaRM the following actions can be triggered automatically,
1) When a requestor creates support message based on an error, service desk employee will be notified automatically
2) A developer will be notified when a change manager in the service desk assigns a developement task assigns.
3) When the developer completes the task, change manager will be notified again.
4) Then, a tester will be notified when change manager assigns a tester.
and many other things also there in the sequence.
Regards,
Satish.

ChaRM and CTS+ for EP 7.0 in SolMan

Hi,
I've been trying to get CHaRM working for EP 7.0 in our SolMan systems for a while, but have not been able to get it working. I've read through and followed all the documentation on the resources page here, the Solution Manager documentation on help.sap.com and service.sap.com and all the notes I can find. We are running SolMan 7.0 SPS 17, and the Portal is on NW7.0 SPS 15.
I have configured SMSY, populated from SLD and assigned to a system (I've tried NETWEAVER 7.0 - Enterprise Portal main instance, and ERP 6.0 - SAP XSS main instance) and assigned the dev and prod systems to a locical component.
I have configured STMS, a single client independant consolidation route from dev to prod. The dev system is defined as a Non-ABAP "source system" in TMS, and I've set the communication system to be the solman system/client.
The CTS+ config all seems to work, I can create/release transports and add objects to transports from the EP dev system.
When I try to implement ChaRM, I create a new maintenance project. I add the portal landscape component to it, and activate change management. This works. When I try to create the task list, it fails trying to create the project IMG for the system. It gives me the error -
IMG project creation error -> see long text
Message no. /TMWFLOW/TASKLIST164
Diagnosis
You want to create a new maintenance cycle. An error has occurred.
When you create a maintenance cycle for a maintenance project in the Solution Manager (SMI project), a project is created in the Central Transport System (CTS project), per logical development system. This CTS project is required as an attribute for the transport requests.
A CTS project is always assigned to an implementation project (IMG project) in the physical system. There must be an IMG project in all physical systems in an SMI project, in which a system change (development/maintenance) can be made.
If there is no IMG project in a system, one is created automatically. The generated IMG project has the same name TEST as the SMI project, but there cannot be an SMI project and an IMG project with the same name in one system, for system-internal reasons.
In SMI project TEST there is a development system in the same physical system SMU as the Solution Manager.
System Response
If one of the development systems is in the same physical system as the Solution Manager, the IMG project cannot be created automatically.
Procedure
Create an IMG project manually in system SMU. In the path: SAP Menu -> Tools -> Solution Manager -> Project Administration.
Choose the SMI project TEST, go to the 'System Landscape' tab, and then the 'IMG Projects' tab.
Select an entry for the system SMU and try to create the IMG project. The system tells you that a system of the same name already exists, and asks you whether you want to choose another project name. Answer 'Yes', and change the project name.
You should then be able to create the task plan.
SMU (solution Manager) is not in the system landscape of this project, I expect that it is trying to create the IMG in this system since this is the communication system for portal dev. However, since it's not in the landscape, it isn't in the IMG tab to be able to create manually as described.
If I try to create the IMG project for the Portal Dev system directly in the project, I get the error -
Error getting RFC destination for logical system EPU
Message no. SMSY_PPMS_API044
Diagnosis
No RFC destination was found for the logical system 'EPU' .
System Response
The RFC connection to the system 'EPU' cannot be created.
Procedure
Create the required RFC connection in the Solution Manger System Landscape Maintenance.
Any advise would be appreciated.
Thanks,
James Blair

Hi James (and others),
I trust you have resolved your issues with ChaRM and CTS+.
If you are running a partuicularly extensive landscape you may want to consider a third party alternative to ChaRM.
Particularly one that integrates with CTS+ (to include non ABAP such as Portal, NWDI Java and so on).
There are several available, the one I am most falimiar with (Note: I do work with Revelation Software Concepts) is Rev-Trac and you can read user reviews at http://www.sdn.sap.com/irj/ecohub/solutions/revtrac
If you run an EcoHub search on Change and Request Management or similar the other alternatives should be returned.
Regards, Rick

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.

Test workbench: test plan, test package, test case, test script, test tools

i want to understand SAP terminology regardsing 'test workbench' terminology - its functions and its sequence.
we creat test plan first , than test pacakge than assign it to tester.
can u give sequence of this tcode and its function if u can provide documentaion too,
tcodes:
STWB_TC
STWB_1
STWB_2
SCAT
AND SECATT
STWB_WORK
i mwan what are the first step to last step regarding Testworkbench.
thanks,
regards.

Hi ,
STWB_TC - Test Case
STWB_1 - Test Catalogue
STWB_2 - Test Organizer
SCAT - Test the object ( CATT) includes recordings ,parameters
AND SECATT - Extended CATT
STWB_WORK - This is a like a worlist to monitor test cases and CATT N ECATT
Now Test Catalogue includes Test cases and test cases includes CATT which has test scripts which is organized in Test organizer .
and to monitor this you use STWB_WORK.
Please reward if useful.

Charm and Test workbench

Similar Messages

Maybe you are looking for