When running in support packs through SPAM, SAINT or SUM there is a requirement to clear out all of the BW Delta queues to ensure that the tables remain consistent.
If you run a support pack or software item / stack into SAP without clearing all the queues you will cause the deltas to go out of sync and they will not function correctly causing the BI / BW guys major headaches doing full data loads, which also require a system outage to accomplish.
When putting support packs live / installing new software, you must have a system outage, so ensure you allow for this in your timelines.
I am assuming here you are installing/updating in client 000 and client 100 is your productive client. (you may have a different setup)
In Client 100 lock out all users except your own, SAP*, DDIC and any other admins working in the system. (If you lock out your own user, SAP* then gives you a backup one for undoing your stuff up :smile: )
If you don't lock out all users then you will find that they use transactions that process data into delta queues that then causes you issues. (like the kind that causes a reload of delta queue data)
Once all users are locked out go to transaction SE38
Run program RMCEXCHK
This program tells you what queues have deltas.
Goto Transaction LBWE in client 100 and process the jobs
Run program RMCEXCHK
See if any other queues are sitting there
You may have to delete Setup Table data.
This is a perfectly normal thing to do and causes BI no issues.
Just follow the instructions that RMCEXCHK gives you (By clicking the error it gives you a link to the transaction to clear out the setup table data)
You can also follow this link for deleting and recreating the setup tables if you want to but there is no requirement in majority of cases to recreate the setup tables.
https://adilmca.wordpress.com/2013/07/14/logistic-data-extraction-from-ecc-6-to-bi/
Now if you run your support pack install you should not see any stops for check requirements phase on open data extraction requests.
