Skip to Content
Author's profile photo Former Member

How to do : manage extractors in case of upgrades with SPAM / SAINT


SAP notes 1081287 and 1083109

Reason and Prerequisites

During the application of support pakage with the transactions SAINT and SPAM, the system sees that there are strippers active, and the following error message


In the case of ST-PI ST / A-PI you can proceed with a skip

For all other ignoring the error can result in loss of data

How to proceed.

1. Delete the setup tables.

To prevent the system from BW going to act directly on the ERP tables, the initial load or full, it creates the setup tables. At the fury of the initial load or full these tables are not used. You can delete them without loss of data.

To understand what “applicationdelete



In our case


To delete them you can use either the bins that the transaction LBWG


2. Empty queues

Each time a user / batch editing an entry, the change is recorded in a queue. Until then the system is in motion, the code will continue to be created. For this reason it is appropriate to proceed with the upgrade at a time in which you can disable access to users.


client                    *

Queque name      MCEX*


qrfc monitor.png


To process the queues need to run the programs RMBWV302 and RMBWV306.

In the production are scheduled JOB



Run the JOB and check that all queues have been processed

Process queues does not mean sending them to the BW system, but simply move the data into other areas, will then be recorded in BW with uploads nightlife.

Caution! Transactions LBWE and LBWG be performed on the principal of which are to be scheduled queues, in our case 120.

If the queues are empty, then you can proceed with the UPGRADE.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Bernd Sieger
      Bernd Sieger

      In 99% of the time you are probably right and emptying queues, setup tables, SM13, ... can be skipped for an ST-PI SP/upgrade.

      However, at least theoretically it is possible that a customer has added a field from an ST-PI package to an extract structure. Also, I have seen ST-PI support packages containing objects from SAP_BASIS. While using fields from ST-PI in an extraction structure from the LO area is really, really improbable, for SAP_BASIS that cannot be assumed, IMHO.

      In that case it is possible that a change to the field's DDIC properties invalidates the stored extraction data (-> delta failing -> new init required).

      So my recommendations is still processing all the extraction data first or at least using the report from SAP Note 1597645.