Tracking state transformation matrices overview

The overview for Tracking state transformation matrices shows the list (9) of all Tracking state transformation matrices configured for the parent workflow in a combined view, and the details of a new matrix or a matrix selected in the list above.

The Back (1) button in the ribbon closes the overview displayed as a modal full screen in the tracking state workflow view.

The Add and Remove (2) buttons can be used to add transformation matrices to the tracking state workflow or to delete already created ones.

The Apply (3) button is used to make changes in the details area before switching to the data of another matrix in the overview.

►IMPORTANT◄ Changes to matrices are not valid and permanently saved until the tracking state workflow as a whole is saved after the Back (1) button is pressed.

The Tracking state type (4) selection field defines which Tracking state type the matrix should apply to. When clicking on Add (2), a new matrix is added that is assigned the default Tracking state type 'Current' (CURRENT).

►NOTE◄ This dropdown changes the type of matrix currently selected in the list and does not switch to the detailed data of another matrix with the selected type!

For each matrix, one of the following options must be selected as the Calculation mode (5):

The rows of the matrix (6) define the previous states (Tracking state codes) for the Tracking state transformations defined as (dis)allowed in the matrix.

• The first row is always the entry >START<, which refers to the special case that the reference object for the Tracking state type does not yet specify a current tracking state entry.
  

  • In the screenshot, the Tracking state codes 'Shipment scheduled' and 'Shipment ready' are allowed as initial tracking states.

• Below this, only the subset of all Tracking state available in the context is typically listed, which defines the configuration for the tracking state workflow ('Available states', see Tracking state workflows) for all associated matrices.

• The sequence of Tracking state codes in the rows is based on the internal names assigned in the master data (Tracking state) (alphabetically ascending). In the example, the internal name was preceded by a code number in each case, so that the sequence in the matrix is oriented to the usual life cycle of a program. The localization for tracking states via Localization does not reflect the relevant code number.

As columns of the matrix (7), the same Tracking state codes appear once again as subsequent states for the Tracking state transformations defined as (in)permissible in the matrix.

• The order of columns for the subsequent states corresponds to the rows for the previous states (6).

Within the matrix (8), each intersection point between row and column determines whether the change from the previous state ('row') to the subsequent state ('column') should be allowed or disallowed .

• In the example, the typical state sequence for a shipment is: (scheduled>) ready > loaded > en route > arrived > unloaded.

• In the event that status messages are issued for each stage of the transport, it is also possible to return from arrived to en route.

• The order can be canceled up to the status loaded (incl.).

• The matrix defines no valid target statuses for unloaded and canceled. For the current workflow, these tracking states are therefore 'end stations'. However, it is quite conceivable that e.g. for canceled orders another tracking state workflow (with other association criteria) is applicable, which defines further permissible Tracking state transformations with the same or other Tracking state codes.

Runtime example:

The selection in the context menu of the ribbon button 'Tracking state'/'Add' (see screenshot below) is restricted in an overview or a details view for a business transaction object (here: shipment), in the context of which the respective tracking state workflow is applicable due to Association criteria. The constraints result from the evaluation of the allowed Tracking state transformations (see the section 'Interactively selectable tracking state codes' there for details) within the Tracking state history against the background of each matrix in the applicable tracking state workflow. The context menu offers all Tracking state codes for selection that have been classified as 'interactively selectable' against the background of at least one matrix.

In the following relatively simple example, an overview shows only shipments with the current tracking state Shipment ready or Shipment scheduled. For the selected shipment with the current tracking state Shipment ready, according to the matrix for the default Tracking state type 'Current' (see above), only the options Shipment loaded and Order canceled are to be added as selectable Tracking state codes:

►NOTE◄ The second configured matrix for the Tracking state type 'Current visible' does not contribute any additional options for the tracking state to be added.