Help Packets MOD009CF5 New from S 39.5.11

• This module contains all migration packets that have been marked as Help packets.
• NEW 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 can be viewed in the module of the same name.
• Help packets concern to the customizing. They show, e.g., questionable customizing which is to be cleaned up.

• This module contains all migration packets that have been marked as Help packets.
• NEW The module is divided into the New packets as well as Failed/open packets areas.
• Completed packets can be viewed in the module of the same name.
• Help packets concern the customizing. They show, e.g., questionable customizing which is to be cleaned up.

• This module contains all migration packets that have been marked as Help packets.
• The module is divided into the New packets as well as Failed packets areas.
• Completed packets can be viewed in the module of the same name.
• Help packets concern the customizing. They show, e.g., questionable customizing which is to be cleaned up.

• indicates that the migration packet has not been executed yet.
• indicates that the migration packet has run successfully.
• indicates that the migration packet has failed. The failure of a migration packet may have several reasons:
  • Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
    • If this is the case, the packet will not be changed. The packet is considered failed.
      • In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
      • If the modification has been carried out or the modification is not necessary, the packet can be set to completed manually by activating the Completed checkbox.
      • As a result, it is moved from the Failed/open packets area to the Completed Packets module.
  • Many help packets check the customizing for problems.
    • If they fail, this means that the customizer must become active.
    • As a result, the positions listed in the logfile have to be checked and modified.
    • If the cause for the failure has been eliminated, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.
• NEW signalizes that this migration packet is still open and waits for another migrationpacket to reach a particular status before it can be run.
• NEW signalizes that this migration packet is not relevant for the current update type due to version dependencies.
• means that this migration packet has been skipped. This status is not used at the moment.

• signalizes that the migration packet has not been executed yet.
• means that this migration packet has been skipped.
• signalizes that the migration packet has failed. The failure of a migration packet may have several reasons:
  • Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
    • If this is the case, the packet will not be changed. The packet is considered failed.
      • In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
      • If the modification has been carried out or the modification is not necessary, the packet can be set to completed manually by activating the Completed checkbox.
      • As a result, it is moved from the Failed packets area to the Completed Packets module.
  • Many help packets check the customizing for problems.
    • If they fail, this means that the customizer must become active.
    • As a result, the positions listed in the logfile have to be checked and modified.
    • If the cause for the failure has been fixed, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.
• means that a migration packet has run successfully.

Note

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

Note

• The sequence of execution of the migration packets is as follows:
  1. PLANTA component (e.g. Server)
  2. Component version (e.g. S 39.5.0)
  3. Packet category (e.g. "Mandatory packet")
  4. Packet name