Mandatory Packets MOD009CEO New from S 39.5.11

• Mandatory packets are the packets that are relevant for a migration. After the migration was carried out, the person that carries out the update must check in this module whether all migration packets have been run.
• 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 are displayed in the module of the same name.

• Mandatory packets are the packets that are relevant for a migration. After the migration was carried out, the person that carries out the update must check in this module whether all migration packets have been run.
• NEW The module is divided into the New packets as well as Failed/open packets areas.
• Completed packets are displayed in the module of the same name.

• Mandatory packets are the packets that are relevant for a migration. After the migration was carried out, the person that carries out the update must check in this module whether all migration packets have been run.
• The module is divided into the New packets as well as Failed packets areas.
• Completed packets are displayed in the module of the same name.

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