Auxiliary Packets MOD009CF5

Access

Information

This module contains all migration packets that have been marked as Auxiliary packets.
The module is divided into the New/installed packets as well as Failed/open packets areas.
- Installed packets are only displayed in the New/installed packets area if they are relevant for future migrations.
Completed packets are displayed in the module of the same name.
Auxiliary packets concern the customizing. They have, e.g., a questionable customizing that should be cleaned up.

Legend

signalizes that this migration packet has not yet been executed.
means that the migration packet has run successfully.
signalizes that this migration packet is still pending and waits for another migration packet to reach a certain status before it can be executed.
Signalizes that this migration packet is not relevant for the current update type due to version dependencies.
signalizes that the migration packet has failed. There may be several causes for a packet to fail:
- Many migration packages check whether the customizing on which the fix is based has changed before they are executed.
  - If this is the case, the change to the package is not made and the package is deemed to have failed.
    - In such a case, you have to check in the customizing whether and how the respective change can be made.
    - If the change has been made or if the change is not necessary, the package can be manually set to completed by activating the Completed checkbox.
    - This will move it from the Failed/pending packets area to the Completed Packets module.

Many auxiliary packets check the customizing for problems.
- If they fail, this means that the customizer must act.
- The locations listed in the log file must be checked and adjusted if necessary.
- Once the cause of the failure has been eliminated, the migration packet can be executed again by clicking on the Execute packet button in the Overview of All Previous Runs module.

Note