BeyondERP.Newsletter
Menu

Setup page · Landed cost

Voyage statuses

A setup page where, per cost area, you define the status values that can be assigned to voyages, shipping containers, folios, purchase orders and lines, and whether each status allows modification or deletion.

Used by
Landed cost manager
Business process
Manage freight and transportation
Menu item
ITMStatusTable
Main table
ITMStatusTable
Data entity
ITMShipmentStatusEntity
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page where, per cost area, you define the status values that can be assigned to voyages, shipping containers, folios, purchase orders and lines, and whether each status allows modification or deletion.
What you do hereUse this page to create the status hierarchy that tells users where a voyage is in its journey and to lock a cost area against changes or deletion once it reaches a given status.
ExampleFor example, a company sets up Confirmed, Goods in transit, Received, Ready for costing and Costed for the Voyage cost area, with Delete allowed only at Confirmed.
Voyage statuses page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Set up Voyage statuses

Use this page to create the status hierarchy that tells users where a voyage is in its journey and to lock a cost area against changes or deletion once it reaches a given status.

Steps from Microsoft

  1. Go to Landed cost > Setup > Voyage statuses.
  2. In the Cost area field, select the cost area to define statuses for.
  3. Select New on the Action Pane and enter the Voyage status name and Description.
  4. Select the Modify and Delete check boxes if voyages at this status may be changed or deleted.
  5. Select Mandatory if the status cannot be skipped.
  6. Set Parent to place the status in the hierarchy; statuses can only move downward from parent to child.
  7. Repeat for each status and each cost area.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansTable column
Cost areaThe voyage level (for example voyage, container, folio) whose own set and hierarchy of statuses you are viewing or creating.Microsoft Learn
Voyage statusThe name of the status.Microsoft Learn ShipStatusId
DescriptionA description of the status.Microsoft Learn Description
ModifyWhether users may change voyages that are at this status.Microsoft Learn ShipStatusCanModify
DeleteWhether users may delete voyages that are at this status.Microsoft Learn ShipStatusCanDelete
MandatoryMakes the status a required step that cannot be skipped.Microsoft Learn ShipStatusMandatory
ParentThe status above this one in the hierarchy; statuses can only move downward from a parent to one of its children.Microsoft Learn ShipStatusIdParent

Test checklist

  1. Select a cost area and create the status chain with Parent set on each child.
  2. Clear Modify on Goods in transit, move a voyage to that status and check users can't edit it.
  3. Try to move the voyage back to its parent status and check it isn't allowed.
  4. Check the statuses used on Landed cost parameters > Status updates exist in the chain.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Voyage statusesPer cost area, set up only the statuses you use (typically Confirmed, Goods in transit, Received, Ready for costing, Costed) as a parent-child chain, clearing Modify and Delete on the later statusesStatuses can only move down the hierarchy from parent to child, and the Modify and Delete check boxes are how you lock a cost area once it reaches a status.Building the Parent chain in the wrong order. Status changes, manual or automatic, can only go downward, so a status placed above where it belongs can't be reached.
Solution architect

5Design impact

Can it be undoneReversible: You can add, edit and remove statuses. Changing Modify, Delete or Parent changes which voyages users can edit or delete and which transitions are possible from then on. Microsoft Learn
If you change it laterChanging the Modify, Delete or Parent settings alters which voyages users can edit or delete and which status transitions are possible, because statuses can only move down the hierarchy from a parent to a child. Microsoft Learn
Technical architect

6Technical

Menu itemITMStatusTable Checked in Dynamics 365
FormITMStatusTable Checked in Dynamics 365
TableITMStatusTableShown as “VOYAGE STATUSES” in Record infoKey field: ShipStatusIdChecked in Dynamics 365
Data entitiesITMShipmentStatusEntityVoyage statuses Checked in Dynamics 365
Who can open itPrivilegesMaintain voyage statuses ITMStatusTableMaintainDutiesMaintain Landed cost setup ITMSetupMaintain
1 security roleLanded cost manager ITMManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itLanded cost manager ITMManagerGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=ITMStatusTable
Integrate withITMShipmentStatusEntity data entity Checked in Dynamics 365
Everyone

8Sources

KEEP EXPLORING

More in Landed cost.

Open the other pages and setup steps in this module, or go back to the Atlas Hub to search every page.