Skip to Content

 

Whenever we are upgrading Enhancement Package for ECC (Ex: EHP5) or when we change the structure of standard data source and before we move to quality or production, we will be running the SAP standard report RMCEXCHK to check various tables for entries which has to be cleared. Because Importing Support Packages or Transport request May cause changes to the structures of the logistics data extraction. To prevent data being lost by the changes, you must first process all the ‘data stores’ (tables, queues, updates) that provide logistics data for the extraction.

After running program RMCEXCHK we may get below message depending on system.

 

Error.jpg

 

Now as seen from the above screenshot, we can see that setup tables needs to be cleared for applications 02, 03,

There are two ways to delete the contents of the setup table –

a.) By using t-code SBIW (LBWG).

b.) By using program RMCSBWSETUPDELETE

Here mainly we are concerned with below error message. Even though we clear Update table this message still exists .So we are going to see how to get rid of this error.

 

Error2.jpg

 

Open V3 updating requests found for 03 that is inventory application.

As this is a unserialized update check using T code sm13 if found the entries below steps need to be followed.

  • Call transaction LBWE in all productive clients of the system.

 

Error3.jpg

 

 

But even though we run above steps and found no entries in SM13, the above error keeps coming when we run the SAP standard report RMCEXCHK

Then to make sure are there any entries in Sm13 run with a selection in SM13 with client *, user *, “all” (updates), “From date” on 01.01.1900). If any entries found we can delete from here and if we do not find data and still we are facing with the above error then the reason is as below.

There will be records in the update tables VBMOD and VBDATA even though transaction SM13 does not display any update requests. Some SAP transactions use constructs that result in entries in the update tables VBMOD and VBDATA before the final screen change (call dialog). If the transaction is then cancelled, these records “hang” as an incomplete update request. They are not displayed in transaction SM13 “Update Requests: Initial Screen” and cannot be executed either and thus only consume memory space unnecessarily.

So we can delete incomplete update requests using the program RSM13002.Error4.jpg

 

Execute the program and select the below three options and execute again.

 

 

Error5.jpg

 

 

Now Run the standard report RMCEXCHK and the error will dissappear.

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Shireesha Pole

    Hi
    while executing the RSM13002, it is prompting warning message in SAP as below

    Data inconsistencies may occur when update data is reorgan
    productive system. Still reorganize?

    can we continue with this? or may it impact production data?

    Regards,
    Shireesha

    (0) 

Leave a Reply