cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow Functionality in sequencing functionality -- Test Management

Former Member
0 Kudos

Hi all,

I am trying to implement sequencing functionality in Test Management. The sequencing functionality is working fine except the workflow, which should be triggered when one test case is completed and send a mail to next tester.

Do I need to make any specific settings. I am not able to find out any document which can help me to have this workflow.

Any idea?

Regards,

Smita

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

You can also check the list of triggered actions in TC CRMC_ACTION_JOB

venkatesh_sakthivel
Active Participant
0 Kudos

Hi everyone,

I'm trying to setup the workflow in Solman 7.1 and experiencing some issue on the email triggering.I have applied the BC sets note and configured all the other workflow requirements but its not triggering an email to my testers in the test plan on releasing the testplan.

I checked the job, CRMC_ACTION_JOB -> no jobs got triggered.

what could be the issue ?

Can anyone help me ..

Regards

Venkat

Former Member
0 Kudos

Hi,

First of all you need to run BC set mentioned in oss note 1113726. For this you need proper authorization for BC set transaction. This will take care of the basic customizing needed.

Second, when creating your test plan make sure to add the status profile "DEFAULT". This will make it possible to change statuses in your test plan and also to mark the field "Workflow active" under test plan attributes.

That's basically it. Now e-mails will be sent to all assigned testers when the test plan is released. And when one tester finishes his test then the next tester in the sequence will get an e-mail (for this the necessary SCOT settings have to be done of course). The e-mails are sent via actions on the CRM transactions which are auto created when generating the test plan. You can find these in transaction CRMD_ORDER if you are curious. So the workflow is not an actual SAP workflow where work items are generated. It is simply e-mail based.

One important thing to make the workflow work is to have the proper authorizations for creating transactions. You will not get any error messages if you do not have the authorizations. The test plan will just be created but the underlying transactions will not be created (and consequently no e-mails will be sent). I suggest you do a ST01 authorization trace if you are having problems. Basically, the most important auth. objects are the ones called CRM_ORD* (as far as I recall).

/Anders

Former Member
0 Kudos

Forgot one thing.

The testers assigned to the test plan have to be created as employees in transaction BP and a valid e-mail address has to be maintained on this employee.

/Anders

Former Member
0 Kudos

Thanks Anders,

I am almost there. Now my workflow is active and I am implementing the release functionality.

1) When I released my test plan, a mail went to all the testers at the same time.

2) Tester 1 completed the test and set the status OK with test ended as true

3) Now the next test is in ready to test status, but my tester 2 has not received any e-mail notification. and this is my problem

Also,

1) All test cases of my test plan are visible to all the users

2) Even when the tester 2 has not tested the 2nd test, tester 3 can go and test the test 3 and can even change the 'status' and 'test ended' status. I believe it should not allow.

Any help on this.

Regards,

Smita

Edited by: smita kumar on Apr 4, 2009 12:43 AM

Former Member
0 Kudos

Hi,

It is true that all test cases within a sequence are visible to all testers in the sequence. That makes sens to me. I have also noticed that a tester can do his test even if the preceeding tester has not completed his test. I think this is how SAP designed it. I do not see any way of preventing this.

Regarding your other problem with e-mails not being sent to the next tester I would of course check that the next tester is created as employee in BP and has a valid e-mail address assigned. I assume you have already checked this. Furthermore, I would do the following:

1) Check in transaction SOST if there is a problem with the sending of the e-mails

2) In transaction CRMD_ORDER check if transactions of type TWTP & TWSQ have been created successfully for your test plan. A document of type TWSQ will be created for every sequence I believe. And on the actions tab in CRMD_ORDER you can see what actions have been triggered. If the lamp is green it has been triggered successfully. It will say "Next Test Case is Ready to Test" when e-mails are sent to next tester in sequence.

3) If you are still not able to trigger the e-mail I suggest you go to debugging. There is a class called CL_AGSTWB_CE_APL_WORKFLOW which seems to control the test sequencing workflow. Try putting breakpoints in some of the methods (e.g. CREATE_OBJ_SQ_TESTCASE_NEXT) and see what happens when you complete the first step in a sequence.

/Anders

Former Member
0 Kudos

Thanks Anders,

The 2nd step what you are suggesting in CRMD_orders.. somehow I am not able to find out how to find it.

Can you let me know the steps..

My SolMAn is on SP16 with Addon installed for this sequencing functionality.

Appreciate all your help so far. I am almost there.

Regards,

Smita

Former Member
0 Kudos

Your info about support package level i interesting. I am on SP18 (aka EHP1) and it was actually my impression that test workflow was not available in earlier SPs. But you mention an add-on regarding this workflow functionality. I am not aware of the contents of this add-on.

Anyway, there are some thing you can check to see if you have the same functionality available as I have.

1) Check in SPRO if you have the following customizing entry:

IMG -> SAP Solution Manager -> Scenario Specific Settings -> Test Management -> Extended Configuration -> Workflow (under workflow there should be 6 items).

2) Check in transaction SE24 if your system has the class CL_AGSTWB_CE_APL_WORKFLOW

3) Under workflow customizing item called "Set-Up Workflow" check that the transaction types TWTP and TWSQ are assigned. If not you should try to run the BC_SET again

Assuming that everything above is okay I suggest you follow up on your users authorizations. Try to give them SAP_ALL to make sure that there are no authorization issues.

An alternative to checking in CRMD_ORDER is to check in the table where the transactions are stored. It is called CRMD_ORDERADM_H. There you can also check if the transactions are generated when you generate your test plan.

Former Member
0 Kudos

Hi Anders,

Thanks a lot for spending so much time for my problem.

As per your suggestion I checked all settings are there. Only small difference

SAP Solution Manager -> Configuration -> Scenario-Specific Settings -> Implementation -> Testing -> Workflow

Here 6 items are there except a node "Information" where only documentataion is there.

All other settings are there as per your suggestion.. even SAP_ALL.

My problem is that the email is generated and being sent as soon as I release test plan to all the tester. I believe it should go to the first tester and once first tester done with testing it should go to next tester. Let me know if you have any clue on this.

Thanks again for your help.

Regards,

Smita

And the details for the Add on is available in note no 1140258, 1109650, 1137832

Former Member
0 Kudos

It is true that all testers receive an e-mail when the test plan is released. Not only to the first tester in a sequence. This is also how it works in my system. I guess it makes sense that all testers are informed that the test is starting even though they are not the first testers. This way they know a little ahead that there is work for them to be done.

However, when the first tester completes his test (by marking the field "Test ended") then an e-mail is sent via an action to the next tester in the sequence. So there is the initial e-mail to all testers and then the subsequent e-mails to the next tester in the sequence.

Furthermore, an e-mail will be sent to the new tester if you subsequently substitute one tester with another tester in a sequence. And if a tester is removed from a test he will also receive an e-mail. And finally, if the test plan manager stops a test package in test plan management an e-mail notification is sent to all testers of this package.

Former Member
0 Kudos

Thanks Anders,

I have sent this weird problem to SAP. Will post the solution into this thread.

Points has been awarded to you. Great help.

Regards,

Smita

Former Member
0 Kudos

Hello there guys,

You probably already noticed that they raised a SAP Note to fix this problem ( note 1327409 ) but I am not able to get the next tester email yet...

Are you still having this problem Smita?

Former Member
0 Kudos

hi Avila,

You need to install the note # 1327409 and then still if mail is not going to next tester. Check the authorization failure in SU53. Lot of auth required for this. this should help.

-Smita

Former Member
0 Kudos

More than SAP_ALL ?

Actually I am just trying to do easy things such a test sequence with 2 simple steps and two users only... the AGSTWB_TP_PACK_RELEASED mail is being sent then the other one sayings its being protected when I change the test plan status but nothing for the NEXT TESTER.... both users have SAP_ALL and different mails.

If anyone of you can help me, I would like to check if the Default settings for Action Definition (on the SPPFCADM -> Action Definition for CRM_ORDER ) for the object TWSQ0001 the action type TWSQ0001_MAIL_TESTCASE_NEXT is "SATISFIED CONDITION IF 0 E0002" .

if you have something different than that I will appreciate any hint... SAP Support is already on it and anything new I will post here for your record, thanks for the help!

05/27/2009 **************************

Issue discovered by SAP related to the language I am using ( it only works in ENglish for now ) and they will see whats happening... thanks for these posts that were really informative.

Edited by: Fernando Avila on May 27, 2009 10:36 PM

Former Member
0 Kudos

Dear all,

I came to this discussion when searching for answers I had on the same problem: in my case it was that some authorizations were missing, which could be solved by applying the respective role out of the security guide:

SAP_STWB_WORKFLOW_CREATE

Maybe this helps someone!

Regards

Martin