How can ProNovia products be uninstalled from an SAP system?
The following steps must be performed to uninstall a ProNovia product from an SAP system:
Definition of the ProNovia namespace
The namespaces /PRONOVIA/ and /PCH/ must be defined on the corresponding system. For more information, see the Knowledge Base article ProNovia namespaces /PRONOVIA/ and /PCH/ for repairs.
Removing custom product bindings and extensions
Any customer-specific integrations must be removed. Please refer to the Integration and Enhancement document available in the download section under the heading "UTI: SAP Integration, Basic Library, Trace" to identify the integration points. If you want to remove only certain products, make sure that you do not remove integrations that are still needed by other products.
If the products have been enhanced by implicit enhancements, these must be rolled back manually because these object are in the customer namespace.
Creating a local workbench order
A local workbench request is required to delete ProNovia Repository objects. To do this, create a new Workbench request using transaction SE01 and remove the transport target so that the request is used as a local request.
Deleting the ProNovia Repository objects
To delete the ProNovia objects the report /PRONOVIA/RSUNINSTALL can be used. The report expects the specification of one or more packages and the previously created transport request. The report deletes all ProNovia objects of the selected packages irrevocably (but not the packages themselves). SAP standard functionalities are used to ensure data consistency. Since some of these functions cannot be used in a completely dark manner, various confirmation popups may appear. Furthermore, the use of SAP delete functions ensures that objects can only be deleted when there are no more usages. Therefore, the deletion report runs through all objects several times until all dependencies are removed and the objects are completely deleted. For this reason, confirmation popups for the same object sometimes appear multiple times.
Sometimes popups appear indicating that objects are still in use. In these popups, force the deletion. Due to cross references, objects can only be deleted in isolated cases if cross references are removed manually beforehand. This applies to the following objects, among others:
Tables cannot be deleted because they are used by domains. There is a circular reference between tables, data elements and domains because domains use the table as a check table. In this case, change the domain and remove the check table.
Tables cannot be deleted because they are used by finding aids. There is a circular relationship between the table and the search help, because the search help is based on a table, but the search help is in turn entered in this table as a search help. Change the table and remove the search help link for the corresponding search help.
Note that the deletion report is part of the /PRONOVIA/BASIC package and is not deleted if the /PRONOVIA/BASIC package is to be deleted. In this case, the report must be deleted manually with transaction SE80 after deleting all other objects..
Transferring the objects into transportable request
In order to be able to delete the deleted objects on the other systems and since the local transport request is not transportable, the object list of the local request must be transferred into a new transport request of the type "Transport of copies". You can also create a request of the type "transport of copies" using transaction SE01, but you must manually enter the target system of the request in the creation dialog.
To transfer the deleted objects, go to the detailed data of the created request, switch to change mode, switch to the Objects tab and execute the "Include objects" function. This is available as a pushbutton or via the menu Order/Task → Object list → Add objects. In the subsequent popup, you can enter the transport request or task of the previously used local request so that all objects are taken over.
If the objects were taken over correctly, you can delete the local request. To do this, you must first unlock the task. To do this, you can use the Unlock objects function in transaction SE03. After successfully unlocking the task, you can delete it and the request.
Release of the transport request
Releasing the transport request is a mandatory prerequisite for later deleting the empty ProNovia packages as well. If an automatic import is planned on the target system, prevent it or make sure that the request has already been imported with the deconstruction of the customer-specific product bindings (see 2.).
Deleting the packages
Only after the order with the deleted objects has been released, the packages can also be deleted. To do this, use transaction SE80, select the packages individually and delete them. A local transport request is required, but this can be created interactively.
Subsequently, also for deleting the packages, the contents of the transport request must be transferred into a transportable request of the type "Transport of copies" (see 5.).
Transport
In order to remove the deleted objects on the other systems as well, the created requests must be imported in the following order.
Workbench request with the product integrations removed
Request with the deleted ProNovia Repository objects
Request with the deleted ProNovia packages
The import of these requests may take some time and should be imported at off-peak times or during a maintenance window due to the integration with SAP standard process. Further, the table buffers must be initialized. This is done by entering the command "/$TAB" (without quotes) in the OK-Code field in the upper left corner of the SAP Gui. This may explicitly only be done at off-peak times. In this context, please contact the SAP Basis administrators.