Messages issue in stwb_work (Service desk)

[Former Member]

Hi, everyone!

I'm having an issue regarding the display of messages opened by users during the tests in stwb_work.

After saving the message, it is not shown under the "Messages" tab, even after refreshing:

http://img4.imageshack.us/img4/1621/stwbwork.jpg

But if I access s_smc_47000016 or s_smc_47000017, I'm able to see them:

http://img542.imageshack.us/img542/7384/ssmc47000017.jpg

Does anyone have any ideas why this is happening?

Thanks in advance,

Felipe Assef

[Former Member · Accepted solution]

Hi Felipe,

We are on Solman 7.01 sp 27 SAPKITL437. The notes mentioned below are not really applying to our case.

Message is created successfully but it is not assigned to the project or test.

Do you have any ideas of how to check this? Any table?

regards,
Davide

[Former Member · Accepted solution]

Hi Davide,

Take a look on my answer for this thread: http://scn.sap.com/thread/3189267

It may help in your case

kind regards, Fabricius

[Former Member · Accepted solution]

Hi Fabricius, I checked your thread. Very helpful but not enough yet.

Where you say:

"The most common reason why messages are not displayed in STWB_WORK is

that the BASIS(ABA) message is missing. Which seems to be just your case.

The reason for this could be that the BASIS Message is not created at all by missing

customizing or that the number range for the BASIS Message has been reset."

I checked the dno_notif and CRM_servic number intervals and they looks fine. The only suspicious thing is that current number in dno_notif is set to 0 . Does this means that the number range interval has been reset?

here the intervals:

009999000000     009999999999    999002359

000000000001     000000999999                  X

008000000000     008999999999    0

How do I check if the BASIS(ABA) message is beeing created? In transaction S_SMC_47000017 everything appears correctly.

tx,

Davide

[Former Member · Accepted solution]

All,

a possible solution to this topic is here http://scn.sap.com/thread/3189267

regards,
davide

[Former Member · Accepted solution]

Hi, everyone!

It was, indeed, a problem with the number range.

In transaction DNO_NOTIF, I created an interval for the Basis(ABA) message and the CRM-Message and everything worked fine.

Thanks for all the support, especially from Vikram Jain who replied my message in SAP Support.

Kind regards,

Felipe

[Former Member]

Hi Felipe,

After creating the message, when the screen came back to the test case, did you pressed the save button in the test case screen before navigating away by typing new transaction or any other way?

Sometimes, by not saving, it can happen that the message is created but not assigned to the test case because the user leaves the transaction before saving the assignment. This can happen by exiting the system or navigating to a different transaction before saving.

If this is not the case, then you probably have an inconsistency there.

Kind regards, Fabricius

[Former Member]

Hi, Fabricius

Thanks for the answer.

Unfortunately, what you suggested doesn't solve the problem.

Kind regards,

Felipe

[Former Member]

Hi

We have exactly the same issue.

After upgrading the Solution Manger 7.1 to SPS4.

Any update for this issue?

Thanks and regards

stefan

[Former Member]

Hi Felipe,

It could be the case described in note # 1676317 - " ISSUE RELATION Correction program".

This note describes a similar issue where the assignment of the messages is lost after the implementation of any of these notes:

  # 1621662 Inconsistent message for duplicated entries in status.

  # 1629156 Incident Messages not displayed in testing workbench.

  # 1633048 Incident Messages not added in status maintenance.

  # 1638507 Message not attached to test case status.

  # 1669638 WC Test Mgmt: should know the exact number message to assign.

  # 1668739 Work Center Test Mgmt: Assign Msg to Test Case not working.

As these note's corrections could be carried by a support package implemented, it is possible that this caused the unassignment of the messages.

Try implementing this note to avoid this problem in future messages and afterwards, run the report  CORRECT_ISSUE_RELATION_TABLES to correct the assignment of the already created messages.

@stefan: this could work in your case too, so maybe you could give it a try.

Kind regards, Fabricius

[Former Member]

Hi, Fabricius

We do have some of the notes you mentioned implemented.

So, as suggested, we tried implementing note 1676317, but we got this error:

"Object directory entry R3TR PROG CORRECT_ISSUE_RELATION_TABLES does not exist"

Any ideas why this is happening?

Kind regards,

Felipe

[Former Member]

Hi Felipe,

this is strange, because the note sould create this report when implementing it. As you mentioned you're in SP04 for Solman 7.1, it should work fine.

Take a look if you're using the version 4 of the note. Also it seems this note will be delivered in SP05, which would be an alternative.

kind regards,

Fabricius

Editing: Apparently, there was another people facing the same error. I belive that the code changes in the note are trying to "change" the report, adding all it's content instead of actually create it from the skecth. I'm currently in contact with the developer responsible to check this.

I'll update here as soon as I get a solution or at least a workaround.

[Former Member]

Hi Felipe,

Try implementing the version 1 of the note and then updating it to version 4.

kind regards, fabricius

[Former Member]

Hi, Fabricius

Sorry for taking this long to give you a feedback about your suggestion.

I talked to my Basis consultant and he told me it wasn't possible to select the version of the note you want to implement. We may only implement its latest version.

Do you have any instructions on how to change that?

Kind regards,

Felipe

[Former Member]

Hi Felipe,

Sorry for the delay, I haven't seen your response before. The note 1676317 should be correct now for implementation.

kind regards, Fabricius

[Former Member]

Hi Fabricius,

We were able to implement the note this time, but It still hasn't solved our problem

(We followed the instructions and also ran the report AGSTWB_MOVE_ISSUE_ST_2_BASIS after, as requested on the note).

I was really optimistic about this one.

Any other possibility?

Kind regards,

Felipe

[Former Member]

Also check:

1621662 Inconsistent message for duplicated entries in status

1629156 Incident Messages not displayed in testing workbench

1633048 Incident Messages not added in status maintenance

1638507 Message not attached to test case status

1669638 WC Test Mgmt: should know the exact number message to assign

1668739 Work Center Test Mgmt: Assign Msg to Test Case not working

Regards

vikram

[Former Member]

Hi, Vikram

Thanks for the answer. The problem, however, persists.

I checked every note you mentioned.

We are running Solution Manager SAPKITL704, and the only notes that were appliable were number 1669638 and 1668739. Still no changes.

Any other suggestions?

Thanks,

Felipe Assef

[Former Member]

HiHi Felipe,

Please implement note: 1638507

thanks

regards

Vikram