MC*SETUP entries in extractor queues" "found; please clean them up"

The following error message prompted during the SUM execution phase JOB_RSVBCHCK_D.

Details from the trace log,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
Phase: JOB_RSVBCHCK_D 
CHECK OF UPDATE TASK ERRORS 
Find the detailed log in RSVBCHCK.SID 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
3 ETG045 ************************************************************************* 
3 ETG011 " " 
3 ETG045 ************************************************************************* 
3 ETG012 "Begin of check for entries in" "extractor queues" 
3 ETG011 " " 
2EETG012 "5711461 MC*SETUP entries in extractor queues" "found; please clean them up" 
2EETG012 "See also long text of message MCEX 141" "using transaction SE91" 
3 ETG011 " " 
2EETG012 "Client 888, application 02:" "265691 MC*SETUP entries found" 
2EETG012 "Client 888, application 03:" "214982 MC*SETUP entries found" 
2EETG012 "Client 888, application 12:" "5043878 MC*SETUP entries found" 
2EETG012 "Client 888, application 17:" "47410 MC*SETUP entries found" 
3 ETG011 " " 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0ITMSETUP""888" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SCLSETUP""888" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SGRSETUP""888" 
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SRVSETUP""888"

Solution

From SAP Note 1705774,

As long as you are in prepare or uptime of the upgrade (upgrade phase JOB_RSVBCHCK2) you can select Ignore
Recommendation: We recommend that you clean up as many updates and RFC calls as possible. Otherwise, you have to clean them up during downtime.
In the downtime there is also a check on update records in phase JOB_RSVBCHCK_D (or JOB_RSVBCHCK_R), which cannot be ignored and must be resolved.

For a smooth upgrade execution, please ensure you have delete / clean up the SMQ1 before the entering the downtime phase. The steps cover as below and you must read the blogs and SAP note from the reference section as well.

MCEX* entries in SMQ1 are zero and do also check SM13 locks are clear.

No entries in RSA7.

Use report RMCEXCHK to check for unprocessed logistics extraction data.

Get advise from developer, BW team for data record deletions from the logistics extraction. Use report RMCEX_SETUP_ENTRIES.

Get advise from developer, BW team for LBWG setup data deletion.

Note: The MC02M_0SRVSETUP cannot be delete by above steps. You can use transaction SE14 to perform the deletion.

# N:\SUM_3\abap\log\RSVBCHCK.SID:
 3 ETG045 *************************************************************************
 3 ETG011 " "
 3 ETG045 *************************************************************************
 3 ETG012 "Begin of check for entries in" "extractor queues"
 3 ETG011 " "
 2EETG012 "265691 MC*SETUP entries in extractor queues" "found; please clean them up"
 2EETG012 "See also long text of message MCEX 141" "using transaction SE91"
 3 ETG011 " "
 2EETG012 "Client 200, application 02:" "265691 MC*SETUP entries found"
 3 ETG011 " "
 A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SRVSETUP""888"