Jan Cavens

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/grid-capabilities

D365 F&O cross-app enables users via saved views and grid control to customize their views/fields/... and save them.

Users can create pivot-like views with the group-by and Totals in all list view pages

This also works on order line forms (SO lines, PO lines, TO lines, ...) but on these forms, the group-by can't be saved.

This means the users needs to recreate their group-by every time they open a sales, purchase or transfer order

Currently the voyage editor is basic in terms of PO and TO line information:

• Expected date (PO and TO)
• PO/TO ID
• Order quantity
• Product and dimensions

This results in a lot of manual work when creating new voyages for PO's or TO's that will not be shipped/delivered in full.

Following data on Inbound orders and Lines to select would increase the ease of use:

TO:

• Expected ship date
• Expected receipt date
• From and to warehouse

PO and TO: Product receipt/Shipment update functions for voyage quantity selection

As is: The order quantity is the only quantity taken into account for voyages. For both PO's as TO's that will be partially delivered/shipped this results in manually updating the voyage quantity.

To be: Quantity selection for voyage lines (as in product receipt/shipment posting)

PO:

• Ordered quantity
• Receive now quantity

TO:

• All
• Ship now
• Reserved quantity
• Available quantity
• Picked quantity

The current selection method in the voyage editor lines to select and Add staging list to shipping container is the 2 options:

• Select all
• Select lines 1 by 1

This means if you have PO or TO of 100 lines that has partial shipment/delivery, for 50 lines, the only way is to select all > unselect 50 lines (click 50 times)

Better approach would be a PO or TO line selection method where user can filter on in both forms on products and do a selection based on that filter.

Currently, it's during voyage creation that the voyage AND containers are created in 1 go.

However, our customer's process is:

1. Shipment booking at forwarder
2. When shipment is done at vendor or subcontractor (for TO's) containerization is done where exact container contents (products, quantities, variants, ...) are registered.

In the landed cost voyage creation process, this is not possible since voyage lines can only be created when container is defined.

Workaround would be:

1. Create shipment + add all lines to dummy container
2. When container content is known: Delete all voyage lines and create new voyage lines with correct containers.
3. Voyage data entities can't be used, since you can't overwrite the container in the line entity (read only)

Foresee same order status field on voyage and container as the purchase order status but then for transfer orders:

1. Created
2. Shipped
3. Received

Now it's only possible to separate TO voyage/containers via filter on PO status ("IS NOT").

Foresee the receiving warehouse where the voyage and/or container will be received.

Now the voyage and shipping container has all shipments receiving at any warehouse within the legal entity.

While container receival planning should be filtered by receival warehouse.

This both for PO as TO voyages

In the D365 voyage editor, partial addition of TO or PO line is possible to add to voyage.

Example:

• TO line qty = 10
• Voyage editor: Transfer quantity = 5

This results in:

• PO --> delivery schedule
• TO --> new TO line

But when performing this via:

• ITMTransferLinesEntity
• ITMPurchaseLinesEntity

You receive following error

A row created in data set LandedCostTransferLines was not published. Error message: 'Write failed for table row of type 'ITMTransferLinesEntity'. Infolog: Error: Voyage lines quantity does not match the transaction quantity for line 5,00 on Transfer order receive..'

Conclusion: TO or PO line split is not possible via data entity