Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Aura panel
summaryIntroduction
paramsJTdCJTIyYm9keSUyMiUzQSU3QiUyMnRleHQlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyMzQ2NTY3MSUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybm9ybWFsJTIyJTJDJTIyZm9udFNpemUlMjIlM0ExNiU3RCU3RCUyQyUyMmhlYWRlciUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzMDE0OWIwJTIyJTdEJTJDJTIyaWNvbiUyMiUzQSU3QiUyMnNpemUlMjIlM0ExOCUyQyUyMm5hbWUlMjIlM0ElMjJib29rLW9wZW4lMjIlMkMlMjJjb2xvciUyMiUzQSUyMiUyM2ZmZiUyMiU3RCU3RCUyQyUyMmhlYWRsaW5lJTIyJTNBJTdCJTIydGV4dCUyMiUzQSU3QiUyMnRleHQlMjIlM0ElMjJJbnRyb2R1Y3Rpb24lMjIlMkMlMjJjb2xvciUyMiUzQSUyMiUyM2ZmZiUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybm9ybWFsJTIyJTJDJTIyZm9udFNpemUlMjIlM0ExOCU3RCUyQyUyMmFsaWdubWVudCUyMiUzQSU3QiUyMmhvcml6b250YWwlMjIlM0ElMjJzdGFydCUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzMDA0OWIwJTIyJTJDJTIyc3R5bGUlMjIlM0ElMjJzb2xpZCUyMiUyQyUyMnRvcCUyMiUzQWZhbHNlJTJDJTIycmlnaHQlMjIlM0FmYWxzZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBZmFsc2UlMkMlMjJ3aWR0aCUyMiUzQTElN0QlN0QlMkMlMjJiYXNlJTIyJTNBJTdCJTIyYm94U2hhZG93JTIyJTNBJTdCJTIyc2hhZG93cyUyMiUzQSU1QiU3QiUyMmNvbG9yJTIyJTNBJTIycmdiYSgwJTJDJTIwMCUyQyUyMDAlMkMlMjAwLjA4KSUyMiUyQyUyMnglMjIlM0EwJTJDJTIyeSUyMiUzQTElMkMlMjJibHVyJTIyJTNBMSUyQyUyMnNwcmVhZCUyMiUzQTAlN0QlMkMlN0IlMjJjb2xvciUyMiUzQSUyMnJnYmEoMCUyQyUyMDAlMkMlMjAwJTJDJTIwMC4xNiklMjIlMkMlMjJ4JTIyJTNBMCUyQyUyMnklMjIlM0ExJTJDJTIyYmx1ciUyMiUzQTMlMkMlMjJzcHJlYWQlMjIlM0ExJTdEJTVEJTdEJTJDJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmZmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyMzAwNDliMCUyMiUyQyUyMnN0eWxlJTIyJTNBJTIyc29saWQlMjIlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJib3R0b20lMjIlM0F0cnVlJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmxlZnQlMjIlM0F0cnVlJTJDJTIycmlnaHQlMjIlM0F0cnVlJTdEJTJDJTIyc2l6ZSUyMiUzQSU3QiU3RCUyQyUyMmJvcmRlclJhZGl1cyUyMiUzQSU3QiUyMnJhZGl1cyUyMiUzQTglN0QlN0QlN0Q=

All tasks/events that have been completed WITHIN THE FILE are displayed in the status system.

  • You can define status types, which will be automatically entered at specific events in the file.

  • You can also manually select the statuses.

The events receive a date and time stamp. The current user is logged as well.

The activation of the Status tabin the order is done in basic data COMPANY → ORDER TAB.

...

Contents

Table of Contents

Basic data

Related pages

...

Field description

Field

Description

Status signal

The status signal displays a green, yellow or red light.

  • ADMIN → STATUS TYPES → STATUS TYPES:
    Select an entry from the dropdown field Status signal:  image2021-8-9_12-37-51-20240403-085204.pngImage Added

Status

Status code, e.g. 001 (Order created)

Description

Description of the status, e.g. Order created or Invoiced

Container no.

Container no.

Actual/Time

Date and time - actual

Estimated/Time

Date and time - estimated

Modified/Time

Date and time - modified

Latest/Time

Date and time - latest

Reference no.

Reference number

Reference

Reference. Can be edited if the status was entered manually

Reference type

Reference type. Can be edited if the status was entered manually

Remark

Field for further remarks and information

who

User login

System date

System date

Time

System time

Level

Level according to status type (Shipment, Container, Tour)

Current

The activated checkbox shows the last status set in the file.

Set status manually

If the checkbox manually has been activated in the master data, all status types that may be set manually are displayed in the status field using the search function.

  • The fields References and Reference type can be filled if the status was entered manually.

  • If a status is added manually to a file, the system evaluates the checkmark Refresh GLA Tracking (statusart_t.gla_track_akt) from the status type.

  • If this checkbox is activated, the file is added to eaxmlsend_t.

The system creates a tracking file that is processed in GLA.

The Reference table from the EDI-Status tab, which is integrated in the lower section, can also be edited in case of a manually entered status.

...

Delete status manually

Authorization object: MANUALSTATUSLOESCH

It is generally not possible to delete status lines from the Status tab.

If the authorization object MANUALSTATUSLOESCH is activated in the master data, it is possible to delete manually or automatically set status lines on the Status tab.

  • To do this, select Delete line in the context menu (right-click) or in the menu bar under Edit.

  • The precondition for deleting a status line is that the checkbox: Manual change is activated for the selected status type

If the manual change is not set for the selected status or the authorization object is not activated, Delete line in the context menu and in the menu bar is greyed out and the status line cannot be deleted.

...

Status with reference to a container number

On the Status tab you can link a status to a container, which is of importance for e.g. eTracking.

Double click into the field Container to see a list with all containers recorded in the file. Select one container per status.

Interfaces may also make this connection when setting a status.

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

The link from the container to the status is only set if the level sea freight/rail/road is switched to container in the status type. Only then a connection can be made.

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

Subsequent changes to the container in the goods description are not synchronized with the Status tab.

Context menu of the status tab

Grouping function

You can group the data by a specific column, e.g. the container number, via the context menu. The table is then displayed per container.

By default, the lines are sorted by status date (actual date) in descending order.