Skip to main content
Skip table of contents

Mandatory Packets MOD009CEO





Access

Information

  • Mandatory packets are the packets relevant for a migration. The person carrying out the update must check in this module after the migration has been carried out whether all migration packages have been executed.
  • 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.

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.

Note

  • Migration packets can only be run individually in this module.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.