ERROR when Trying to create support message in satellite system

[Former Member]

hi all,

I already searched the forum for this error, but still not solved...

I'm working with ECC 6.0 as satellite system and Solman 4.0.

The RFC connections are working fine (tested in SM59 with authorization test).

I also generated and affected the different roles to the User used for the

RFC connections. Number ranges configured properly.

I've read and followed:

Any suggestions?

Please help...

Best regards,

Ivan Schnyder

[DoloresCorrea · Accepted solution]

Hello Ivan,

Xould you give us more details? message number error, how you create the message, from solman, from the satellite..

Note 1011376 must fix the issue usually.

Best regards,

Dolores

[Former Member · Accepted solution]

Hello,

thanks for your quick reply,

I already checked the SAP note,

the param ITEM_PRODUCT_ID was not in the list.

the following error message is called when creating a supMessage

from the <b>satellite</b> system:

<i>Error in local message system; message 000000000014 not complete

Message no. BCOS030</i>

Thanks a lot

[Former Member · Accepted solution]

Hi Ivan

Did you get a solution for this error? I am also getting an exact same error while I try to create a message from my SCM 4.1(6.40 release) to SOLMAN 4.0(7.00 release). The error message it shows me is:

Error in local message system, message 009999000001 is incomplete

Message no. BCOS030

I am trying to look for solution, but haven't come across any...

Let me know if you come across any...

Thanks all

Abhi

[Former Member · Accepted solution]

Hi ALL,

I am on ABA/BASIS Support pack 10 and I have not imported support pack 9 or anything like that and the error given in Note 1011376 - Problems when you create a message after importing SP 9...do not apply to me...

Any suggestions??

Thanks

Abhi

[markus_doehr2 · Accepted solution]

> I am on ABA/BASIS Support pack 10 and I have not

> imported support pack 9 or anything like that and the

if you have 10 then you also have 9, support packages are not cummulative.

--

Markus

[Former Member · Accepted solution]

Hi markus,

I meant in the sense that the error messages mentioned in the SAP note 1011376 - Problems when you create a message after importing SP 9...

do not occur in my case...I am not getting :

Short dump "CX_OS_OBJECT_NOT_FOUND". This error occurs regardless of whether you use transaction NOTIF_CREATE or CRMD_ORDER to create the message.

Short dump "UNCAUGHT_EXCEPTION" occurs when you try to call the condition configuration in transaction SPPFCADM as mentioned in the note.

Do you still recommend That I go ahead and implement that note???

Thanks

Abhi

[Former Member · Accepted solution]

Hi all,

I was also getting the error "Error in local message system; message

010000000203 not complete"

I got that error when the table BCOS_CUST, in the satellite system, had the record.

OSS_MSG W SM_S06CLNT208_BACK CUST620 1.0

SM_S06CLNT208_BACK is associated to the user SOLMANS06 in SM59.

I changed the Dest. for the record with Appl. = OSS_MGS from SM_S06CLNT208_BACK to SM_S06CLNT208_TRUSTED. S06 is my system and 208 is my client.

SM_S06CLNT208_TRUSTED uses my ID to go back to my solution manager system S06 208.

Now I get the message "Message 0100000222 successfully created in Support

Desk System" and creates the support message on my solution manager system.

Hope this helps... It worked for me.

Jason

[raquel_pereiradacunha · Accepted solution]

Hi,

I was getting the same error as Ivan when creating messages from satellite system release 4.6C to my Solution Manager 4.0 SP09 and my problem was solved deleting the param ITEM_PRODUCT_ID and including roles SAP_SUPPDESK_CREATE and SAP_SV_FDB_NOTIF_BC_ADMIN in the UserID assigned to my RFC destination configured in BCOS_CUST

( SM_<SID>CLNT<client>_BACK ).

The UserID SOLMAN<SID> by default does not have authorization to create Service Desk message SLFN.

Regards,

Raquel Cunha

[Former Member]

Hi Guys,

I have the same problem BCOS030. Was the problem solved? I use Solman 4.0 (7.0). I use the trusted RFC. I can give an take the roles to the user - how much I like - everytime the same message...

regards, Stefan

[Former Member]

Hi all

I also struggled with this for 2 weeks. But the problem is fixed.

Do your "normal: config from the IMG and then:

1) Make sure that you have selected for the system NOT to check for the User in SolMan

tr: DNO_CUST04, Go to Detail, Select the field NO_USER_CHECK, "X", this is very important, otherwise you will have to create a username for everyone on the satellite system... far too timeconsuming.

2) In your satellite system under OSS_MSG: Col1:Application: OSS_MSG, Col2: + : W. Col3: RFC Destination: SM_"SOLMANRFC"_BACK. Col4: + : CUST620. COl5: + : 1.0

In the Solman side you maintain Col3 as "NONE".

3) Make sure that ALL users in the satellite system has the following roles: SAP_SUPPDESK_CREATE and SAP_SV_FDB_NOTIF_BC_ADMIN.

4) Make sure that you have TRUSTED RFC to and from your Satellite system and Solution Manager.

The main one to be sure of is: SAP_ALL for all SOLMANxxx user in the Solution Manager system for every satelite system, because the standard roles from SAP does not work.

This should have your Service Desk Messaging working.

Jaco Snyman

[Former Member]

for sure the SAP_ALL do not contain the roles required for SolMan and / or ServiceDesk.

There is an other Message where i have provided the required roles.

[Former Member]

Hi Jaco ....

I have everything working in service desk functionality , even message can be sent from satllite to solution manager system but only when satellite user is having sap_all when i assign SAP_SUPPDESK_CREATE and SAP_SOL_SERVTRANS_CREATE to user in satellite system it throwz an error, saying " Because of error 513, message not created " , I believe the points that you have provided out of that all are correct in my case i have checked all 4 points . can you explain the fourth point again . I can send message from satellite system but only if user in satellite is having sap_all. Please help me out.

[Former Member]

Hi

I have error when create support message in satellite system:

Error in local message system; message 000000000028 incomplete

Message no. B~031

User for RFC have SAP_ALL.

Please help. Thank you

[Former Member]

Hi Roman

Did you solve your problem with creating a message in satellite system? I also have the problem and nothing seems to work.

Jaco Snyman

[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.

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

Regards,

Nikhil

[Former Member]

To use the Destination: SM_<SID>CLNT<000>_BACK

this user commonly "SOLMAN<SID>" in your SolMan-Client

where the ServiceDesk is used, from your ClientSystem needs

the following roles assigned or equivalent:

SAP_BC_AI_LANDSCAPE_DB_RFC

SAP_D_SOLMAN_RFC

SAP_SOLMAN_DIRECTORY_ADMIN

SAP_SUPPDESK_CREATE

SAP_SV_FDB_NOTIF_BC_ADMIN <= this is assigned by the wizard only

and this roles needs to be generated !!

may be you need just only:

SAP_SUPPDESK_CREATE

SAP_SV_FDB_NOTIF_BC_ADMIN

this depends on configuration and the applications

which are using this destination.

This settings are not done by the Wizard of SMSY

where you are creating this connections.

(this valid at least up to SP16 of SolMan - (current at july 2008)

[tharmon]

All,

I have a similar issue. While I can create support messages in our Sandbox BI system, they fail in Dev, even after the same setup of RFC's and BCOS_CUST config.

The new error is:

Error in Local Message System: Function module "/SAPSMOSS/06_CREATE_R3_NOT_ATT" n Message was Not Created

I've checked OSS Notes and other SDN strings, but did not see this function module error. This is in BI 7.0 to a SolMan 4.0 system.

Has anyone seen this before or have a resolution?

Thanks in advance.

~Thomas

[Former Member]

sap note 614311 has the solution to the problem 'Error in the local notifications system: Function module "/SAPMOSS/06_CREATE_R3_NOT_ATT" notification n was not created'

Thanks.

[Former Member]

Hi Ivan,

I am having the same issue here in NZ. Once I've figured it out, I'll let you know.

Cheers, Michael

[Former Member]

Hi all,

I´ve got the same problem like Ivan. There is an error when creating message from satellite system: error in local message system

original message in german:

"Fehler im lokalen Meldungssystem: Die laufende Anwendung hat bewußt einen

Abbruch mi Meldung wurde nicht angelegt

Meldungsnr. BCOS088"

One satellite system is working fine, but creating messages from the other ones I ´ve got this error. The customizing is the same in all satellite systems.

Creating message from:

solution manager system:
C16 ok

satellite system:

C23 ok

C33 error in local message system

C72 error in local message system

I tried following steps:

- I also checked sap note 1011376 but the paramameter ITEM_PRODUCT_ID was not in the list.

- RFC connections are also working fine

- sm30:Table BCOS_CUST

in satellite system:

OSS_MSG W my rfc connection CUST620 1.0

in solman system:

OSS_MSG W NONE CUST620 1.0

It still doesn´t work?

Any ideas?

Regards

Andy

[DoloresCorrea]

Hello Andy,

For error message BCOS088 please check in the involved satellites notes:

52959 & 1000890.

Hope this helps,

Dolores