GCSS / TP-doc not matching in TMS

What impact would it have on your daily tasks in terms of time saving or cost reduction?

JYSK bundle their BLs into TpDocs because of easier process and cheaper customs processes. This means, if JYSK has 5 containers on 5 bookings. But JYSK only want 1 BL. Therefore, they ask us to consolidate the 5 containers into 1 transport document. This means in GCSS that the containers are linked under the individual booking, but the documents are only existing on 1 booking. When the order gets in to TMS, we see the parent transport document reference connected to one single container, but the reference can be connected to another container in GCSS. The problem starts when amendments are done in GCSS and not all bookings in TMS receive amendments as references are not matching.

EX: Gcss ref: 237648386 - reflectin different container numbers from TMS to GCSS

How frequently would you use this improvement?

This is current preveting us from receiving Amendments on the correct booking in TMS

How should it work?

It should be connected to correct FRO and reference number connected to GCSS ref