Support Messages in TestManagement not visible

[Former Member]

Dear *,

When I create a error/support message in TestManagement (STWB_WORK), the message is not listed there.

Message creation works fine, but it is not recognized within the test case message overview.

We have SolMan 7.1.

For historical reason, I would like to create error messages of type SLFN (instead of SMDT).

I made the appropriate changes to the PROCESS_TYPE-Parameter.

Creation and later resolving those error messages works fine - simply the listing is missing.

Does anybody know, how to complete the list of messages in the test case status overview?

Thanks and Regards,

Jan

PS: the image shows the empty message overview:

[Former Member · Accepted solution]

Some additional strange observations:

- When creating the error message, I do not receive a confirmation pop up window (usually it states the message number)

- the error message does not contain technical informations about the system in the long text

- The SAP Attribute section of the support/error message is completely empty.

- the Action section shows a red light for "Create/Change Basis Message from CRM Transaction"

[Former Member · Accepted solution]

Hi Jan,

As you probably know a Supportdesk message consists of two messages

The Basis(ABA) message and the CRM-Message.

The assignment of the messages to the tab in the STWB_WORK transaction

is determined by the ABA(basis) message.

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.

Try running the report: AI_SDK_CUSTOMIZING_LISTING

from transaction SE38 and check  the output of the report.

In addition, check if this note is valid for your SP level:

Number              1638507

Version             1 from 04.10.2011

Short text          Message not attached to test case status

Kind regards, Fabricius

[Former Member · Accepted solution]

Hi Fabricius,

It was indeed the ABA-Message.

The number range object dno_notif had not been set up correctly.

After correcting that everything worked as expected.

Thanks,

Jan

[Former Member · Accepted solution]

HI Jan, I am having the same issue.

how did you check that the object dno_notif was not set up correctly? Ho did you correct it?

davide

[Former Member · Accepted solution]

Dear all, thanks to Fabricius and the SAP support our issue is now fixed.

The problem seems to be caused by the number range. In table
DNOD_NOTIF is possible to find 3025 entries.

The highest number that ever happened is 9999002455, while the
transaction DNO_NOTIF shows a current number 9999002409.

Basically, in trasnaciton DNO_NOTIF the current number has to be set
higher than the highest number ever eg. to 9999002500

I changed the number accordingly and the problem has now being solved.

Regards,
Davide