error 513 while raising the message from satellite system

[Former Member]

Hello All,

When I try to send message(Service desk) from satellite system, i get following message

"Because of error 513, no message was creat

Support Desk System"

I gusses there is some problem with authorisation.

please guide how can I fix this issue.

Regards,

Shyam.

[Former Member · Accepted solution]

Thanks all,

Nothing worked, now iam just checking from begning whether anything has gone wrong

[prakhar_saxena · Accepted solution]

Hi,

goto Solman

TA -

---

SLG1 here press execute and check details for the error.

also check this note

Note 864195 - Error 513 when you enter Support Desk Message

it might be of some help to you

Regards

Prakhar

[Former Member]

Hi Gurus,

I have assigned customized action profile to SLFN transaction.

When I try to send message(Service desk) from satellite system, I get following message

"Because of error 513, no message was created

Support Desk System"

But when we check in crm_dno_monitor , the message is created at the backend,but without assigning external number range.

Whenever I am making any modification in action profile, it is creating the first messgae after restart

of SAP Solman System, but for next message, Error 513 message is raised and message is created at backend without assigning external number to it

I think there is some problem in number range or buffer in number range

Can some one help me in this

regards

Swati

[Former Member]

I haven't seen this error in a long time - are you using an older release of Solution Manager? Have you activated all the Service Desk BC sets?

This error usually means - as you state - that there is a problem with the number ranges. Check that the internal number range assigned to the SLF1 message has the same values as the EXTERNAL number range assigned to your SLFN message. When I say "values" here, I mean the same numbers to be assigned (ex. 1 to 999999999) rather than the NR identifier (01). Later BC sets corrected this, but you used to have to do it manually.

Give this a try and let us know what happens.

Lori

[Former Member]

Hi,

I think the problem is solved.

Thanks to all

Regards,

Shyam.

[Former Member]

hi,

i am getting the same error message 513. Can you please tell me what u did to solve it

[prakhar_saxena]

Can you post tickets directly in solman system if so then there is prb in satellite only with authorizatio or RFC but if not in solman then check

If business partner for the user is generated as a reporter in solman

If so pls chec using BP transaction goto that bp and enter into general role change mode.

now here goto identification tab check the entry for the corresponding system can be solman or satelite from which user is creating.

Also if this doesnt solves ur problem then,Do check this blog for config service desk again if you have missed anything

/people/bruyneel.guillaume/blog/2008/05/02/service-desk-implementation-guide-part-i

Hope it solves the problem

Regards

Prakhar

[Former Member]

Hello Subhashini,

I followed the steps given in tht link. but that dint help.

Following are the roles i hve assigned to user in backrfc

ZRFC with authorisation object S_RFC and S_RFCACL

SAP_SUPPDESK_CREATE

SAP_SUPPDESK_ADMIN

SAP_SV_FDB_NOTIF_BC_ADMIN

SAP_SV_FDB_NOTIF_BC_CREATE

SAP_S_RFCACL

and following roles for user creating the message

SAP_SUPPDESK_CREATE

SAP_SMWORK_BASIC

SAP_SMWORK_INCIDENT_MAN

SAP_SUPPDESK_ADMIN

ZRFC

with SAP_ALL profile

I have also checked the action profile...SLFN0001_STANDARD_DNO

is maintained in dno_cust01

I have also defined the number ranges... is there anything else to be done.

Regards,

Shyam

[Former Member]

Hi,

This is no. range related problem. Go to DNO_NOTIF and CRMC_NR_RA_SERVICE and make both no. rage internal - internal and external - external insted of internal - external and external - internal.

Aslo asssign RFC authorization to user.

Then assign this new no. range to SLFN. then check.

Regards,

Nikhil

[Former Member]

Hi,

You can check this link it tells about the missing authorization.

If you still face the problem, just check the Action profile assigned or not. if not assign the action definition to ur action profile. SLFN0001_STANDARD_DNO

this will solve the issue.

Regards,

Subhashini.

[Former Member]

I still dint find a solution, I followed all the steps given in

thread, but still i get the same message.

[Former Member]

I got the answer for this.

Thanks