Skip to main content

Information

By 12/04/2022C.T. M.I.S.

As part of the upgrade of our services and the continuous effort to improve them, soon we will deploy the new Container Terminal Operating System. In this section you will find useful information for the new system.

 

New XML messages– v.30 (19.5.2022) [7z]

 

New EDI messages (25.10.2022)

Any agent that wants, can send to Container Terminal of ThPA the below EDI messages, instead of the corresponding XML messages [zip]

 

Indicative list of ports’ UNLOCODE [pdf] 

 

Register to the New SEMPO Information System (for sending / receiving XML messages)

To register to the new SEMPO system it is necessary to submit an electronic application for inclusion at https://webportal.thpa.gr (Instructions for use: webportal_user_manual_EN)

 

Register to the New Truck Appointment System (TAS)

 

Information about the Representatives register (WEB and / or REST API)

The new system allows representatives of agents or authorization holders to send COREOR & COHAOR messages.
For the inclusion of representatives, it is necessary to register at https://webportal.thpa.gr (Instructions for use: webportal_user_manual_EN)
Then the representatives must enter the details of the companies or people they represent at https://ctosxml.thpa.gr (Instructions for use: ctos_xml_manual_for_respresentatives_v1_EN)

Once the application is accepted, they will be able to send the new COREOR (container release order) and COHAOR (request for control) messages on behalf of the companies or individuals registered in the system.

* (It is possible to send via web application https://ctosxml.thpa.gr and through REST API. For sending the technical details contact us at tos@thpa.gr)

 

[accordion] [acc_item title=”Maiden call: What should I do before announcing the arrival of CALINF?”]Before sending the CALINF I must inform the Vessel Planning Department about the arrival of the new ship and send them detailed files for the construction of the ship, which must contain the following information::

  • Stack weights holds/decks
  • Slots only for 45’ (positions)
  • Slots only for 40’
  • Slots only for 20’
  • MAX HC under deck per bay
  • Special DG positions
  • RF slots (positions needed)
  • Type of Hatch covers
  • Position of vessel gear
[/acc_item] [acc_item title=”ΜΚ666/BG888: In the old messages I declared the ports of transit cargo this way. What about now?”]The new system contains all UNLOCODES, so the corresponding port must be declared with its UN LOCODE.[/acc_item] [acc_item title=”The ship’s port rotation has changed. Should I do something?”]Yes. When the port rotation changes and before I send any XML, except CALINF, I have to inform the Berth Planning Department for the new port rotation and then proceed to send XML messages. [/acc_item] [acc_item title=”In XML / EDI we use corporate internal port codes and not UNLOCODES, what can I do about it?”]In that case I inform the Documentation Department about the internal code and the UNLOCODE to which it corresponds. After the update I can send the XML / EDI normally.[/acc_item] [acc_item title=”Creating a new service. What should I do?”]When a new service is about to arrive at the port, I must inform the Berth Planning Department about the following:

  • Service name
  • Port rotation (UNLOCODES)
  • Shipping line
[/acc_item] [acc_item title=”The port of unloading of a container has not been set yet. What should I declare in the EDI / XML messages?”]Since the port of unloading the container is unknown, I use the code XXOPT. Before sending the EDI / XML I must make sure that I have informed the Berth Planning Department about using the XXOPT code. [/acc_item] [acc_item title=”Package Type: Which are the acceptable values of the field?”]The acceptable values of the Package Type field are the following:

1: PACKAGES

2: BOXES

3: PALLETS

25: BULK

53: BUCKETS

55: BARRELS

56: BAGS

57: ROLLS

58: CONTAINERS

59: PIECES

[/acc_item] [acc_item title=”I want to declare an OOG container. Which fields must I fill in?”]When I want to declare an OOG, I fill in at least one of the corresponding OOG XML / EDI fields.[/acc_item] [acc_item title=”How is a new voyage created?”]To create a new voyage, it is necessary to send a CALINF and fill in the fields: Vo_code, i/b code, o/b code with unique code and for vessel name you enter the name of the ship as it was registered in the system during the creation of the vessel definition. When the system receives a CALINF it checks if it has been preceded by another one with the same characteristics. In case there is no other such CALINF, the new voyage is created, otherwise it updates the existing voyage with the new information.[/acc_item] [acc_item title=”I want to change the Containers that were declared with COPRAR loading (or unloading) and will be loaded on the ship. What should I do?”]A new COPRAR loading message must be sent, which will include ONLY the Containers that need to be loaded. Upon receiving the message, the system will DELETE the old loading (or unloading) COPRAR and will register the new message. [/acc_item] [acc_item title=”While sending COPRAR1, I received an error message “Slot operator does not exist“ “]This message means that I have not declared the corresponding box operator for one or more containers. I need to inform the Berth Planning Department about the existence of this box operator and resend the message.[/acc_item] [acc_item title=”While sending COPRAR2, I received an error message “port is not in the rotation of this service“ “]This message means that I have not declared the correct port rotation for the ship. I need to inform the Berth Planning Department about the correct port rotation and resend the message.[/acc_item] [acc_item title=”I want to release a Container for Pick Up by road. What should I do?”]In addition to the Customs procedures, for the container release it is necessary to send a COREOR message (https://ctosxml.thpa.gr). This message is the pre-announcement for the release of a container by notifying CT of the following information. This message is sent by the holder of the delivery order or a representative.

  1. Issuer of the delivery order
  2. Last holder of the delivery order
  3. Invoicee – where the invoice will be issued
  4. Owner of the cargo
  5. The date of departure from Container Terminal, for the charge of the storage rights etc.
  6. Relevant Customs documents
  7. The haulier for the automatic dispatch of the exit permit (optional)
[/acc_item] [acc_item title=”I received an error message “Clearance date must be future date.“ when sending a message.”] The above message means that I have entered a previous date or time. It is better to leave the time field as it is. [/acc_item] [acc_item title=”I received an error message “Sender is not equal to Last_Holder Or Sender is not exist in the representatives of the holder“ when sending a message.”] The above message means that I have not registered the holder as my customer, or that I have passed the wrong ID. Always, the one we put in the “Order Holder” field should be shown in the “Holders Projection”. If it doesn’t show, I can add him via “New Delivery Order Holders”. [/acc_item] [acc_item title=”I sent COHAOR with the wrong handling code. What should I do?”] I resend the message, with the correct code and contact with the Documentation Department to cancel my previous COHAOR. [/acc_item] [acc_item title=”How should I write the delivery order number?”] The delivery order number should be written exactly as in the order, with punctuation, capital letters, etc. [/acc_item] [acc_item title=”I don’t receive a success/failure notification of my message, what should I do?”] I need to indicate the email to which I want to receive the reply via “Account Management“. I enter the email, select XML Responses and click submit. [/acc_item] [acc_item title=”I am not receiving invoices, what should I do?”] I need to indicate the email to which I want to receive the invoice via “Account Management“. I enter the email, select ANNEX and click submit. [/acc_item] [acc_item title=”I am not receiving exit permits, what should I do?”] I need to indicate the email to which I want to receive the exit permission via “Account Manager“. I enter the email, select Exit Permit and click submit. [/acc_item] [acc_item title=”The carrier is not receiving exit permits, what should I do?”] I have to enter the carrier’s email address in Coreor , in the field “Carrier Email Address“. [/acc_item] [acc_item title=”I want to monitor the status of the Container license, what should I do?”] To keep track of the stages, I go to “Permits Status“, type in the Container Number and click the search button. [/acc_item] [acc_item title=”How should I use the fields with the blue search button?”]
  1. At first, I enter (Name or ID)
  2. I press the blue search button.
  3. I type again.
  4. I select the line ([id]Name) that appears.
[/acc_item] [acc_item title=”How can I find the Id of someone in the system?”] In order to find someone’s ID, I insert the Vat of the company and press the search button at “Company Data” page. [/acc_item] [/accordion]
This site is registered on wpml.org as a development site.