Versions Compared

Version Old Version 3 New Version Current
Changes made by

ProNovia

Marcel Schifferle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

  • SAP does not provide a way to uninstall entire packages. Only individual objects can be deleted.

  • A test installation should therefore generally ONLY be performed on a sandbox system that can be deleted again.

  • The steps listed below are time-consuming despite the utility, depending on the amount of installed products.

  • Due to the lack of SAP support for uninstallation, individual objects may remain in the system despite the steps described below.

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:

...

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).

Note

If uninstalling PCF or DMC-PCF, do not uninstall from top packages including all children if AFW / DMC-AFW is installed. This old packages include a common package which are used by these.

  • PCF (/PRONOVIA/PCF) → do not uninstall /PRONOVIA/PCF_COMMON, but instead unsinstall all relevant packages separately:

    • /PRONOVIA/PCF_WI_WD

    • /PRONOVIA/PCF_WI

    • /PRONOVIA/PCF_UI_FORM

    • /PRONOVIA/PCF_UI_COMP_WD

    • /PRONOVIA/PCF_UI_COMP

    • /PRONOVIA/PCF_UI_WD

    • /PRONOVIA/PCF_UI

    • /PRONOVIA/PCF_OBJ

    • /PRONOVIA/PCF_MAIN_WD

    • /PRONOVIA/PLG

    • /PRONOVIA/PLGAPI

    • /PRONOVIA/PCF_EHP2

    • /PRONOVIA/PCF_BO

    • /PRONOVIA/PCF

  • DMC-PCF (PRONOVIA/DMC) → do not uninstall /PRONOVIA/DMC_COMMON, but instead unsinstall all relevant packages separately:

    • /PRONOVIA/DMC_WI_WD

    • /PRONOVIA/DMC_WI

    • /PRONOVIA/DMC_UI_ACTIONS

    • /PRONOVIA/DMC_UI

    • /PRONOVIA/DMC_OBJ_HANDLER

    • /PRONOVIA/DMC_MAIN_WD

    • /PRONOVIA/DMC_MAIN

    • /PRONOVIA/DMC_DD

    • /PRONOVIA/DMC_BO

    • /PRONOVIA/DMC

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.

...

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.paragraf above: Removing custom product bindings and extensions).

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.paragraf above: Transferring the objects into transportable request).

Transport

In order to remove the deleted objects on the other systems as well, the created requests must be imported in the following order.

  1. Workbench request with the product integrations removed

  2. Request with the deleted ProNovia Repository objects

  3. 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.

...