First Mile Ideas Portal
What impact would it have on your daily tasks in terms of time saving or cost reduction? |
This will mitigate price calculation errors and ensure always correct weight band selection by deducting tare weight from |
How frequently would you use this improvement? |
Every day |
How should it work? |
For import shipments where exact cargo weight is always known, SAP TMS should use Stuffing weight of container available in GCSS (or actual weight from RKEM/Comet) for weight band (rate) selection, rather than current logic of calculating cargo weight by deducting tare weight from VGM declared in GCSS. Current logic is prone to error in cases when VGM declared with allowed margin of discrepancies, and may result in lower of higher weight band selected if cargo weights close to the limit separating neighboring weight bands. Also for locations were rates are based on VGM this will allow for more exact VGM calculation by summing up actual cargo/stuffing weight with tare weight |
Hello @Guest
Recent changes in GCSS (release 103, deployed 4th of July) should mitigate incorrect net weight calculations done in TMS, as GCSS will, when possible, always refer to the actual tare weight at container number level, rather than the average weight of container types.
Any changes to the logic of how TMS calculates net weight would be up for a bigger review.
@Gerardo Leo for reference
Thanks!