SAP Patch Assembly/Distribution Engine (SPADE) (BC-UPG-OCS) 
SAP Patch Assembly/Distribution Engine (SPADE) (BC-UPG-OCS)
Use
Using Transaction SPADE, SAP partners can create their own
Conflict Resolution Transports (CRTs) or Collective CRTs for their add-ons and offer them to their customers.CRTs are necessary if the add-on from an SAP partner modifies parts of the SAP standard. Here, there is danger that the changed objects may be overwritten when importing Support Packages.
Therefore, the SAP Patch Manager (SPAM) always checks if there are conflicts between the installed add-ons and the Support Packages to be applied. If this is the case, the Support Package import is terminated with a corresponding message (in SPAM step ADDON_CONFLICTS_?). To be able to continue, you must have resolved all conflicts using CRTs.
For add-ons delivered by SAP, the relevant CRTs are offered in the SAPNet R/3 frontend or in the SAPNet Web frontend. You can request and download CRTs from there. After the queue has been completed with the required CRTs, you can continue with the importing the Support Packages.
Since SAP partners cannot offer their own CRTs in the SAPNet, they have to make them available to their customers in another way.
Not that a CRT resolves conflicts between one Support Package and one add-on. A Collective CRT resolves conflicts between a series of continuos Support Packages and one add-on.
In SAP terminology, the term patch has been replaced by Support Package.
Note that you can only use this transaction with SAP GUI for Java and SAP GUI for Windows.
Prerequisites
The SAP Patch Assembly/Distribution Engine (SPADE) can be installed on any SAP System with Release 4.0 or higher, on which the newest SPAM/SAINT update has already been imported. Transaction SPADE is included in the standard SAP System as of Release 4.6A.
Call Transaction SPADE (client 000).
Functions
Activities