Skip to main content
Deutsch (Deutschland) Español Français (France) Italiano Polski Slovenčina (Česko)

Search

search shadow

Articles in this section

See more

Ocean Shipment Creation Errors and Recommended Actions

Rich Hellinga
Rich Hellinga
Updated

In this article

The table below lists the Ocean Shipment creation Root Cause Analysis (RCA) errors and the recommended actions for fixing those issues.

Root Cause Error

Recommended Actions

Carrier Not Identified

Issue: No matching carrier was identified in our network for the SCAC in the shipment creation request.

Recommended Action:

  1. Validate that the specified carrier SCAC was a part of the Implementation Scope or Statement of Work (SOW) outlined in the contract.

  2. Verify that the correct carrier SCAC has been provided in the shipment creation request.

  3. If both validations are successful, reach out to project44 support via this link and raise a "Carrier Integration Request" ticket for additional assistance.

Customer Not Configured for Carrier

Issue: The customer is not configured for carrier SCAC that was specified in the shipment creation request.

Recommended Action:

Reach out to project44 support via this link and raise a "Carrier Integration Request" ticket for assistance in resolving the matter. The team will guide you with the necessary steps in obtaining the carrier configuration.

Unsupported Shipment Identifiers in Request

Issue: The provided shipment identifier in the creation request is not supported by the carrier.

Recommended Action:

  1. Kindly retry the shipment creation using a supported shipment identifier type for this carrier.

  2. If the problem persists after retrying, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Invalid Carrier Code in Shipment

Issue: The format of the carrier SCAC in the shipment identifier is invalid in the creation request.

Recommended Action: Please review and update the shipment creation request so that it contains the correct carrier SCAC format, which must be four capital letters.

Example: "ABCD"

Invalid Container Number in Shipment

Issue: The format of the container number in the shipment identifier is invalid in the creation request.

Recommended Action:

  1. Please review and update the shipment creation request so that it contains the correct container number format, which must consist of four uppercase letters followed by seven digits.

  2. The first three uppercase letters should denote the BIC code of the owner of the container.

  3. The next uppercase letter should represent the category of the equipment identifier: U for freight containers, J for detachable freight container equipment, or Z for trailers and chassis.

  4. The next six digits should depict the serial number assigned to the container.

  5. The final digit is intended to serve as the check digit, providing a means to validate the accuracy of recording and transmitting the BIC code and the serial number. You can calculate or validate the check digit here.

Link: https://www.bic-code.org/check-digit-calculator/

Example: "BICU1234567"

Invalid Booking Number or MBOL in Shipment Identifier

Issue: The format of the booking number or master bill of lading in the shipment identifier is invalid in the creation request.

Recommended Action: Please review and update the shipment creation request so that it contains the correct booking number or master bill of lading format, which must have a minimum length of 6 characters and a maximum length of 45 characters. Additionally, they must contain at least one number.

Example: "ABC123DEF", "ABCDEFGHIJ1"

Customer Account Details Not Recognized

Issue: No valid accounts in our system match the provided customer account details in the shipment creation request.

Recommended Action: Review and update the correct account details you have provided in the shipment creation request and validate them against the account details that you provided during implementation.

Temporary Issue with Service

Issue: There was a temporary service interruption.

Recommended Action: If you notice that this issue is continuously affecting a significant number of your shipments over an extended time period, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Contract Date Outside Range

Issue: The shipment creation request contains a contract date that is too far in the past.

Recommended Action: Review and update the container tracking date so that it is within the last twelve months.

Invalid Tag IDs in Request

Issue: The Tag IDs within the shipment creation request are invalid.

Recommended Action: Review and update the correct Tag IDs you have provided in the shipment creation request and validate them against the Tag IDs that you provided during implementation.

Inadequate Permissions

Issue: The customer does not have the necessary permissions for shipment creation.

Recommended Action: Reach out to project44 support via this link and raise a "Support Request" ticket to ensure that you have the correct permissions for creating a shipment.

Related articles