on 02-19-2014 6:22 AM
Hello,
We have a lot of entries in SM13 in V1 status processed, why does not dessapear from SM13?
How to review the update status was created fine on data base? Which the problem UPD2 records?
As per my knowledge, only remains in SM13 the canceled update request in V2, but I don't know why we have v1 green processed record and no desapear from SM13.
Any advice?
Regards,
Hello
At first check if you have V2 update work process defined (instance parameter rdisp/wp_no_vb2)
Check in the system log if there were not some message about V2 updates queue overflow (eg: Q0 G Request (type UP2) cannot be processed).
Some statistics update (MCF_STATISTICS_UPD_V2) are waiting to be processed.
If there is one update only you can process it manually.
Regards
671037 - Update records in INIT status without R/3 locks
In transaction SM51 (menu 'Go to -> Queue Info' or 'Go To -> Server -> Information -> Queue Info', you cannot detect any queue overflows (which can be determined by indentical values in the columns 'max wart Req' and 'max Req'). In addition, if an overflow occurs, entries exist in file dev_disp (starting with 'DpRqIPutIntoQ: Overflow').
In the t-code SM13, there are a lot of records with the status "V1 update completed" , they are waiting for V2 update process.
For those updates which still have not been automatically processed in t-code SM13, please schedule the program RSM13005 as a background job to process them. More details, please refer to the SAP Note 140357.
140357 - MCE_STATISTICS_UPD_V3, MCEX_UPDATE_02:COLL.RUN INIT
1510367 - Re-processing failed update records via SM13
In SM13 transaction mark the records to be processed/re-processed, then click on the pull down menue "Update requests-Repeat Update"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.