Skip to Content
0

spam error

Jun 15, 2017 at 01:29 PM

123

avatar image

Hi gurus,

runnin SPAM transaction in client 000 I got the following message

At least one semaphore for another system ID and/or client range exests .

Could you helo me?

thanks and regards

Giovanni

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

avatar image
Former Member Jun 16, 2017 at 06:42 AM
0

Hi Giovanni,

this error should only occur, if the affected system was part of a system copy, where in the source system a SPAM or SAINT queue was not confirmed at the time of system copy export has started.

Can you confirm this?`

Unfortunately there is not yet an official solution for that. Please open an SAP incident on component BC-UPG-OCS-SPA.

Cheers,
Andreas

P.S.: In case you open an incident then you can request me in the incident to fix this. Please also tell me the number here and ensure that a system connection to client 000 is open

Share
10 |10000 characters needed characters left characters exceeded
Ilke Tutku Senol Jun 16, 2017 at 06:24 AM
0

I have same error.

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Unfortunately there is not yet an official solution for that. Please open an SAP incident on component BC-UPG-OCS-SPA.

Cheers,
Andreas

P.S.: In case you open an incident then you can request me in the incident to fix this. Please also tell me the number here and ensure that a system connection to client 000 is open

1

Hello Andreas,

I've already opened an incident and SAP consultants solved that issue. But when I asked about the solution they answered like you said, there is no official solution.

0
Giovanni Baglio Jun 19, 2017 at 01:30 PM
0

Hi Andreas,

I can confirm what you said regrding system copy

Giovanni

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Giovanni,

in this case you have the option to confirm the queue and do the copy again or you open an incident and we will fix it.

Best,
Andreas

0