Task #19648: Booking container Jerq Issue on deletion + Cannot use container in a new booking Issue - level-3-support - Redmine

Actions

Copy link

Task #19648

open

Booking container Jerq Issue on deletion + Cannot use container in a new booking Issue

Added by Redmine Admin 5 months ago. Updated 3 months ago.

Status:

New

Priority:

High

Assignee:

Start date:

04/07/2026

Due date:

04/07/2026 (about 5 months late)

% Done:

Estimated time:

0:00 h

Spent time:

2:00 h

GitLab ID:

4134

GitLab Milestone:

GitLab Ticket Number:

786

GitLab Time Logged:

7200

Lock Timeline Date:

gitlab project trace:

Description

Below is the scenario:

Container CNTA is currently active in CCS with ATPA and booking BK1
User tries to use this container CNTA in a new booking, e.g. BKXYZ, but is unable to do so and given message "Container Ref CNTA is still valid on ATP ATPA and Booking No BK1."
Naturally upon seeing this message, the user tries to delete the CNTA, BK1, ATPA record in OceanCCS
New issue is faced now with customs response beimg given as "CNTA-Container is already Jerq"
User will now contact MACCS to resolve this issue.

RCA & comment: No 'quick fix' solution exist other than force marking the container as 'completed' in OceanCCS since this container is in 'jerq' status at Customs.

Solution proposed:

Ask customs to provide us with a regular list of 'jerq' containers
WRT above scenario, cater it smartly within system usign the customs response from Customs. e.g. On seeing the jerq status, mark the container as completed in system such that the user will be allowed to re-use this container in OceanCCS in another booking.

GitLab Sync Log

[{"id": "41624", "author": "Nirmal Shibchurn", "hours": 2.0, "created": "2026-04-07T07:40:42.775Z", "log_date": "2026-04-07", "comment": "Imported from GitLab by @Nirmal Shibchurn on 2026-04-07T07:40:42.775Z: 2h-(2.0)h spend at: 2026-04-07", "status": "active", "deleted_by": "", "redmine_entry_id": 12903}]