SAP recently discovered a problem after the import of transports using transaction SPAM or SAINT with parallel R3trans processes or during an upgrade or update with the Software Update Manager (SUM). After the import or update/upgrade, some ABAP sources can be missing from table REPOSRC. This may, for example, result in program terminations with the error message SYNTAX_ERROR in a wide range of programs. During an upgrade or update, a termination occurs in the SUM with, for example, the error BATCH_SCHEDULING_FAILED. This primarily affects large function groups or classes, but it is unpredictable, which ones will be affected.
The problem has been documented in SAP Note 2147596. If you already experienced the problem, you can repair your system by transporting the missing object from another SAP system at the same release and support package level (e.g. development or test system). If you have problems with that, please open an incident in the SAP support system for component BC-DB-DB4.
If you are planning to import transports through transaction SPAM or SAINT without the required patches, make sure that you do not run R3trans in parallel. To verify or change this, choose menu option Extras -> Settings and choose 1 for the “Number of parallel processes per R3trans” and for the “Max. Number of Parallel R3trans Processes”.
If you have configured parallel import processes for your transport landscape as described in SAP note 1127194, deactivate parallelism as long as you did not implement the required patches on all SAP systems in your landscape. To verify the parallelism setting, check the transport profile /usr/sap/<transdir>/bin/TP_DOMAIN_<SID>.PFL (where <transdir> is your transport directory and <SID> the system ID of your transport domain controller system). Search for the line "parallel = ...", which defines the degree of parallelism used by the transport tools, and set the value of parallelism to 1 to turn off the feature.
If you are planning an upgrade or update through the Software Update Manager (SUM), make sure that you follow the instructions in SAP Note 2147596.
Updated April 22nd, 2015: In the meantime, an SAP patch is available for most versions and SAP Note 2147596 has been updated accordingly.
