Changes to Order Viewer user interface (Supply Planning)

Reason for change: To improve usability of the Order Viewer and working with defined order types.

Result:

Order viewer now displays information pertinent to the order type, replacing generic Item and Location fields. This aligns the Order Viewer details with Add Orders screens introduced in version 20.x. This change is applicable to transactional data measures linked to Order Mapping in the Replenishment Engine associated with the Cycle. These fields are displayed by order type:

  • Transfer Orders: Source, Destination and Transport Method.
  • Purchase Orders: Location and Supplier
  • Production Orders: Process Item, Process Location and Process Version.

These fields can be modified in the Order Viewer when accessed through the edit mode.

The Show Transactional Data menu and screen have been removed from this release. Order types not linked to Order Mapping in the Replenishment Engine are displayed in the Order Viewer by selecting the Other option.

Action required after upgrade:

The Order Viewer improvements for order types requires a valid Replenishment Engine defined in the associated Cycle configuration. Users must ensure that all required attributes are defined in the Replenishment Engine's Supply Allocation Mapping.

It is recommended to append the supply planning template (spls.zip) for this version. If that is not possible, one can extract and append the Replenishment Engine definition from the template zip (spls.zip > EngineSettings\ReplenishmentEngineSetting\Supply\SPLS_ReplenishmentEngine.xml).

Alternatively, if using an existing or non-standard replenishment engine, users can verify the configuration by placing the definition in Edit (Configuration > Cycles > Engines, modifying at least one field to trigger the validation, and Save (the field can be modified and reverted). This validates that all mandatory fields for the new version are populated.

If it is not possible to populate the required data, or users require to maintain the Add Transactional Data and Order Viewer details from previous versions, the Replenishment Engine can be removed from the associated Cycle configuration. This is not recommended as it affects the process to Commit Orders (from Planned to Fixed) and disables other usability features in this release.