Mandatory Packets MOD009CEO | Customizing

Access

Information

Mandatory packets are the packets 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/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 the migration packet has not been run yet.
signalizes that a migration packet has run successfully.
signalizes that this migration packet is still open and waits for another migrationpacket to reach a particular status before it can be run.
signalizes that this migration packet is not relevant for the current update type due to version dependencies.
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 run and 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 was carried out or the modification is not necessary, the packet may 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.

Note