Skip to Content
Author's profile photo Jerry Wang
Jerry Wang
July 28, 2014 1 minute read

An example to fix Generic stop set error status in tcode SMQ1

I have Q7Q/504 as ERP system and QDD/504 as CRM system.

A new material named JERRY2 is newly created in ERP and successfully downloaded to CRM via request download.

However, after that I made changes on material in ERP, and the change fails to be synchronized to CRM. When checking the outbound queue status via tcode SMQ1, I see the status Stop.

When I tried to reactivate the Queue,

/wp-content/uploads/2014/07/clipboard1_506906.png

I got the following message “Generic stop set”:

/wp-content/uploads/2014/07/clipboard2_506907.png

I have debugged to know why this message is raised:

/wp-content/uploads/2014/07/clipboard3_506908.png

the flag sg_lock is marked as abap_true, so the message is raised:

/wp-content/uploads/2014/07/clipboard4_506915.png

The root cause is because there are some errorous entries existing in table trfcqout:

/wp-content/uploads/2014/07/clipboard5_506916.png

/wp-content/uploads/2014/07/clipboard6_506918.png

/wp-content/uploads/2014/07/clipboard7_506919.png

Just remove them in tcode SMQ1 and repeat the operation to trigger delta download, this time everything works.

/wp-content/uploads/2014/07/clipboard8_506920.png

There is now no status STOP in outbound queue, and the delta change on ERP has been successfully synchronized to CRM ,which could be observed in tcode SMW01.

/wp-content/uploads/2014/07/clipboard9_506924.png

Assigned Tags

      7 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Sagar Mopagar
      Sagar Mopagar

      Hi Jerry,

      I found your answer not only helpful but also very clear and easy. Thanks a lot for your post.

      Best Regards,

      Sagar

      Author's profile photo Zhendong Tang
      Zhendong Tang

      Hi, Jerry, where is this post, I cannot find it anymore, only the topic is there, have you delete it?

      Author's profile photo Jerry Wang
      Jerry Wang
      Blog Post Author

      Hello Zhendong,

      I never delete it. The url of post: https://blogs.sap.com/2014/07/28/an-example-to-fix-generic-stop-set-error-status-in-tcode-smq1/

      Best regards,
      Jerry

      Author's profile photo Zhendong Tang
      Zhendong Tang

      Hi, Jerry,
      it appears this time , thank you,  and thank you for your blogs, I would take a good look at them.

      Regards.

      Tang

      Author's profile photo Shubham Gupta
      Shubham Gupta

      Hi Jerry,

      Very Helpful content.

      Thank you!

      Author's profile photo Vinay Kabde
      Vinay Kabde

      Thank you. You had the issue/fix very thoroughly documented. Very helpful.

      Author's profile photo Thomas Deubel
      Thomas Deubel

      The question must be: Why does the system behave like this?

      The answer is given in the following note: 430980 - CRM Server: Analysis in delta data exchange R/3->CRM -> Step 9a:

      In general, this is not an error. In this case, check whether the initial load for the object or its child object is still running. During this time, the delta queues are locked to prevent the transfer of newer delta data until the completion of the initial load. In this case you must wait until the initial load is complete, afterwards the system automatically removes the STOP entries. For test purposes you can force the manual start of the delta queues with a potential loss of the data consistency by deleting lock entries R3AD_<object name>* in Transaction SMQ1 in the R/3 BACKEND System. For the analysis of errors in the initial load, refer to Note 429423.