Because of error 513, no message was created in Support Desk System

[former_member334238]

Hai All,

We have recently updated Solution manager 4.0 version

When we try to create a support message in Solution Manager we are getting an error message:

"Because of error 513, no message was created in Support Desk System"

We on currently on SP10.

Kindly help us out please?

Regards,

Chin.

[Former Member]

Sorry for not responding for a while - i've been on holiday.

I added the 02 number range as per the thread

but this still didn't work.

I am wondering if i have a problem with the BC sets, because when I created the Sold-to-Party partner I had no option to select the customer group SOL_Customergroup?

Mark

[Former Member]

Hi Mark

Please look at the SAP note 1011376. That solved my problem. Hope it works for you too

Regards

Bilal Nazir

[Former Member]

Hey there

Did anybody find any solution to this issue.

We also have the same configuration and facing the same issue !

In fact I am now not even able to forward a previously created message to SAP.

Regards

Bilal

[Former Member]

Did you remove the external number range "02" as I described in my earlier posts above?

[Former Member]

Yep , I did that . But it had no effect !

-Bilal

[Former Member]

SAP_ALL rules! Who would have thunk it but I just added SAP_ALL & SAP_NEW to the user SOLMAN<SID>, i.e. SOLMANPRD on the Solution Manager system and it fixed the problem:

I tried to create one message and I got the 513 error.

Added SAP_ALL & SAP_NEW

I was able to create the message without error.

Now that I look back at the previous posts, John Jarvis suggested checking the auth's previously.

Since this user is also used for the customizing scout and maybe other scenarios I don't want to remove SAP_ALL for now and I don't have time to research all the authorizations required. If SAP is watching and figures out what roles and profiles the SOLMAN<SID> user is supposed to have please post. Note 834534 doesn't clarify it.

Message was edited by:

David Hill

[Former Member]

Hi David,

You are right, my problem with "Because of error 513, no message was created in Support Desk System" was caused by authorization problem. But as described in note 864195 there is several reasons for this error.

Profiles SAP_ALL & SAP_NEW are working well but it is enought to add role SAP_SOCM_CHANGE_MANAGER (Accept or reject change requests)

to user from RFC connection, check in this link ->

http://help.sap.com/saphelp_nw04/helpdata/en/45/cb27429d16db2ce10000000a1550b0/content.htm

... and just for info, this role also solved the error on R/3 systems ->

"Error in local message system: You do not have authorization to create a notifica Message was not created"

Best Regards

[Former Member]

HI all,

The note 498984 solves this problem....

rgds,

anand

[Former Member]

At least I am in good company. I am getting the same error.

Note 498984 appears to be for an old release of SolMan. Note 614311 points back to 498984.

Oddly the Service Desk works on a prototype system that had ST version 8. The new install (not upgrade) of Service Release 2 (ST is level 9) doesn’t work.

I can’t find a difference in the two systems in DNO_NOTIF or DNO_CUST01. I suspect a BC Set.

Here is what I found regarding note 498984, has anyone else had any luck?

a) Change the number range as follows:

In transaction DNO_NOTIF >> Button 'Groups' (I assume the 'Change' button).

The note says "Select 'Group without text' SLF1 and choose 'Group --> Insert'"

The words 'Group without text' does not exist. Do they mean the "Not assigned"? Below is are all that is on the screen:

X Basic Notification

SLF1

X Basic Notification

ABSC TASK

X ABA Message SLF1

Not assigned

The it says to "Maintain text: 'SAP Support Message' and maintain a number interval from - to." What should the values in the interval be? Just leave them blank our actually put in a '-' and a '.'?

b) Delete or change the status profile in Customizing:

In transaction DNO_CUST01 >> Entry 'SLF1' >> Button 'Details' the 'Status profile' field is already blank so there is nothing for me to do. I even tried putting something in, saving, then deleting it; no luck.

If anyone has found the answer, please help. Thank you,

David

[Former Member]

I applied SP stack 10 and that seems to have fixed it.

Also note that SAP changed the numbering between the ABA and CRM message, they are no longer synchronized, see note 1054063. The external interval 02 doesn't exist for CRM_SERVIC.

[Former Member]

David

Do you know what support pack actually fixed this? I am using ST 4.00 Level 10 Support package SAPKITL420 and get exactly the same problem as everyone else.

The oss notes don't seem to help.

I feel like I'm going round in circles on this one.

Thanks

Mark

[Former Member]

Hi Mark,

I had it fixed for a while and now I am on SP12 and the error is back. I think when I activate BC sets it puts the entry I describe below back. I have a message in to SAP and am trying to get a final answer. The quick answer until they update either the IMG or a note is to remove the external number range 02 from the SLFN transaction type. Below is some of my message to SAP:

There is a contradiction in SAP documentation: The IMG activity ‘Check number range for Service Desk Message’ says to do the following:

In this IMG activity, you check the internal and external number ranges to the Service Desk.

Activities

1. Select the transaction type SLFN.

2. Choose Goto -> Details.

3. Check the internal number range 01 and the external number range 02 under Transaction / Numbering.

4. Save your changes.

This is impossible. You can not save the screen because number range 02 does not exist. This also appears to contradict note 1054063. Who is correct, the people who wrote the IMG or the people who wrote the OSS note?

SAP delivers a value '02' for the SLFN transaction type external number range in all the BC sets. However the number range object CRM_SERVIC does not have an external number range so the transaction is inconsistent.

Every time I apply a support pack or activate a BC set it breaks the Service Desk. This leads to the error ‘Because of error 513, no message was created in Support Desk’.

SAP development needs to fix this so it doesn’t keep appearing. When the client applies a support package a year from now they should not have to deal with this issue.

I believe I have two choices and I want to make the correct one so will wait for SAP advice:

1) Remove 02 from the external number range field of transaction type SLFN

2) Add an internal number range 02 to CRM_SERVIC.

[Former Member]

Thanks David.

Let me know if SAP come up with a proper solution. Do you think anyone has a live implementation of Service Desk & Change Management in version 4.0 of SM?

Most of the documentation is incorrect in some way & every step of config requires another trawl through oss and sdn!!!!

Thanks again. It's good to see I'm not the only one going crazy!

Mark

[Former Member]

Hi Mark,

You mean you don't find SAP documentation complete and straightforward? It's much better than it used to be though.

Yes I'm sure there are lot's of Service Desk's out there. I wish I had access to someone with CRM knowledge, that would sure make it easier.

Did removing the '02' fix the error for you?

[marc_resch]

Hi,

did anyone slove this problem with the note? I having the same problem and the note doesn't work.

Regards

Marc

[Former Member]

i have been trying to assign the intervals that the note indicates into SLF1 , but it does not work . Did someone found whats up?

Basic Notification - SLF1

009999000000

009999999999

Basic Notification - ABSC TASK

000000000001

000000999999

Aba Message SLF1

008000000000

008999999999

[Former Member]

Check your authorization on the Solution Manager side. The userid used in the RFC defined in table BCOS_CUST (Transaction SM30 to access) must have the necessary authorization to create a service desk ticket.

[former_member195032]

Hi Billy Wong,

There is SAP note on this issue.

Note 498984 - Error 513 when sending support message

This will solve your issue.This contains some manual changes.

Please see another note

614311 - FAQ: Support notifications

regards,nishant

Please reward points if this helps

[Former Member]

Hello,

I have the same problem after SPS 10 on SOLMAN 4 and tried to solve according note 498984. I'm not succeed. On what system I should implement this note: on SOLMAN or satelite one.

Regards,

Tomasz Lejzak