Common data >  Logistics tables >  Logistics tracking template  

Display all Hide all

Use this function to create logistics tracking templates.
For each template, define the steps required during the flow of goods.

This setup is used to perform a logistic tracking at the logistics chain level and more particularly at the shipment and/or transportation level.

Prerequisites

SEEREFERTTO See the documentation on Implementation.

Screen management

Entry screen

Presentation

In order to create the template, you need to:

  • assign it a reference,
  • indicate if the template applies to the shipment and/or transportation process,
  • activate the template
  • and define, as a sequence, the steps you require to track the flow.

A template is only used to initialize the logistics tracking. The template and tracking are not permanently linked: you can delete the template at all times. Changes to a template do not apply to the tracking processes using this template.

Close

Field

The following fields are present in this tab:

Name of the block

  • Tracking number (field TRKNUM)

The tracking number is mandatory. This can also be a free code or reference.
  • Description (DESAXX field)

This long description is used as a title in screens and reports.

By default, the short title, the long title or the column header for a piece of data are recorded (on creation/modification) in the connection language of the user.
You can add your translation in another language using the Translation function :

  • Click Translation from the Actions icon in the related field.
  • In the Translationwindow, add a new language code and your translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as the default language of the folder.
  • Shipment (field SHIPFLG)

Select this check box so the template becomes available at the shipment tracking level.
  • Transport (field TRNPFLG)

Select this check box so the template becomes available at the transport tracking level.
  • Active (field ENAFLG)

This check box is used to specify if the template is enabled or not.
When a template is disabled, it can no longer be used to define a new tracking at the shipment or transport level.
  • Sequence (field TRKSORT)

The steps are defined as a sequence. The sequence number of the steps is not available for entry or modification. This number is incremented automatically with each line addition/insertion.
  • Step (field TRKCOD)

Each line in the template corresponds to a step. The steps are defined as a sequence. You can add lines by clicking the Add icon at the top of the table. You can also insert new steps: click Insert from the Actions icon, displayed at line start.
Click Selection in the Stepfield and choose a predefined step from miscellaneous table 108.

You can only modify or delete a step which is not related to a dependent step (i.e. not a parent step).
  • Mandatory (field TRKMDY)

Specify if this step is mandatory or not.

To define a dependent relationship with a parent step, you must set this parent step as Mandatory.
Example: for step 4 to be dependent on step 2, step 2 must be Mandatory.
  • Dependency (field TRKDEPCOD)

You can define a dependent relationship between steps, using a step called parent step.
For a step to be selected as the parent step, it must have the following characteristics:

  • the step is included in the template,
  • it is defined as Mandatory,
  • it is set before the dependent step.
    • Once you have chosen the parent step, its description is displayed, followed by the sequence number of the step in order to differentiate other possible identical steps.

    Close

    Error messages

    In addition to the generic error messages, the following messages can appear during the entry :

    All error messages are generic error messages.


    Tables used

    SEEREFERTTO See the documentation on Implementation.