Project

General

Profile

Actions
Copy link

Task #19314

closed

Export : Change of Vessel

Added by Redmine Admin about 1 month ago. Updated about 6 hours ago.

Status:
Closed
Priority:
High
Assignee:
-
Start date:
01/18/2026
Due date:
01/19/2026
% Done:

100%

Estimated time:
0:00 h
Spent time:
9:00 h
GitLab ID:
3716
GitLab Milestone:
GitLab Ticket Number:
753
GitLab Time Logged:
32400
Lock Timeline Date:
No
gitlab project trace:

Description

We have encountered a scenario where a vessel change is performed on CCS from Vessel A to Vessel B. Subsequently, later on, the shipping agent changes the vessel back from Vessel B to Vessel A for the same container. When this occurs, the COPARN generated and sent to CMS is ignored, and an error message is returned by CMS, as shown below.

Booking Number - 265047566 

image.png{width=919 height=26}

We would be grateful if you could do a workaround for the above scenario to ensure that, once a vessel change has been completed and validated, the shipping agent is unable to roll back the container to the previous vessel.

GitLab Sync Log

[{"id": "37516", "author": "Jeremy Roussel", "hours": 2.0, "created": "2026-01-22T06:05:15.552Z", "log_date": "2026-01-18", "comment": "Imported from GitLab by @Jeremy Roussel on 2026-01-22T06:05:15.552Z: 2h-(2.0)h spend at: 2026-01-18", "status": "active", "deleted_by": "", "redmine_entry_id": 12025}, {"id": "37550", "author": "Jeremy Roussel", "hours": 7.0, "created": "2026-01-22T11:42:09.306Z", "log_date": "2026-01-21", "comment": "Imported from GitLab by @Jeremy Roussel on 2026-01-22T11:42:09.306Z: 7h-(7.0)h spend at: 2026-01-21", "status": "active", "deleted_by": "", "redmine_entry_id": 12036}]

Actions
Copy link

Also available in: Atom PDF