Contents
Related topics
Field description of the Container tab
Field | Description | Examples/Basic data | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
File Qty Type | The number of datasets is displayed on the left. The example shows a booking with
|  | |||||||||||||||
Edit quantity | Use the local menu on the right side to edit the quantity.  Thus, the fields Quantity and Container type can be edited. | Add line:  | |||||||||||||||
Oversize | You can enter and transmit a checkmark Oversize with the corresponding dimensions per container. These fields can be integrated into the container tab of the goods description in the order using the mask editor. If the booking was created from an order, these values are automatically pre-assigned with values from the order. The Checkbox Oversize is displayed in the booking by deault. Additional dimension fields appear once you activate the checkbox. If the Oversize checkbox is active if dimensions have been entered in the booking, the interface will transmit these values as well. If the checkbox is active but dimensions are missing, the sending process will terminate. |  | |||||||||||||||
Mode of transport | This field is transmitted per container line and must NOT be changed within a booking. Merchant/Merchant is pre-assigned for new bookings. The mode of transport is pre-assigned based on the field Service type. The mode of transport can be changed in the 1st container line on the Container tab without affecting the field Service type in the header data of the booking.
|      | |||||||||||||||
Shipper's owned | Checkbox to mark this container as Shipper's owned. This pre-assignment of the Shippers' Owned indicator in the booking can be prevented by setting a global database holder: → If you are interested, please get in touch with our Service Desk. | ||||||||||||||||
Reefer details | Details to the reefer data entry, see chapter below. | ||||||||||||||||
The following applies to the next 3 address fields The addresses must be recorded in the address basic data to enable the transmission - as addresses in the OceanBooking are pre-assigned with details from the basic data. | |||||||||||||||||
Pickup address | = Empty container pickup Usually returned by the carrier along with the booking confirmation. | ||||||||||||||||
Ship from address | = Empty container positioning, provided that the carrier is responsible for the pickup. Required field for Carriers Haulage. We recommend using a dummy address with name if the address is still unknown at the time of the booking. If the booking was created from an order, this address can be pre-assigned with the corresponding values from the order. | ||||||||||||||||
Ship to address | = Delivery address in the receiving country, provided that the carrier is responsible for the delivery. Required field for Carriers Haulage. We recommend using a dummy address with name if the address is still unknown at the time of the booking. If the booking was created from an order, this address can be pre-assigned with the corresponding values from the order. | ||||||||||||||||
Date/Time |
| NOTE: If the address is filled, the date MUST be entered in bookings for Evergreen. | |||||||||||||||
Contact details Contact | You can enter contact details (contact, phone, fax, email) for the addresses Ship from/to. These fields are pre-assigned automatically once the corresponding partners have been filled in the address. A selection window opens of an address contains multiple partners. Here you can select the correct partner for the address. These fields can be edited. | ||||||||||||||||
Enter stopover | You can enter stopovers if you have selected one of the servicetypes Door to Pier/Door to Door. Stopovers can be entered with a reference and time. If you are using the function Addresses per container and if addresses have been recorded in the goods description → Container → Addresses in the order, these are automatically pre-assigned as stopovers in the booking. | The qualifiers VGM/VET/CSTOP/PUP are automatically accepted into the booking. | |||||||||||||||
Remarks | Free text for information: 2 lines with 512 characters each. Double click into the remark fields to open the search for text modules. Select one or more text modules and accept them into the fields. | ||||||||||||||||
Field description for reefer data
When manually entering a booking, you can enter reefer details on the Container tab.
Field | Function |
|---|---|
Temperature/ unit | Value and unit for temperature |
Airflow
| Value and unit: [CBM per hour] or [SCF per hour] |
Humidity in % | Humidity value in percent |
Non Active Reefer | Y/N |
Generator required | Y/N |
Pre cooling required | Y/N |
Ventilation | Y/N |
Control Atmosphere | Y/N |
Field pre cooling required
This field is automatically filled with the corresponding text when you accept data from an order and if the checkbox Pre cooling required is active.
Not all carriers process the checkbox Pre cooling required. If this checkbox is activated, the text Pre-Cooling Requested=YES must therefore additionally be entered in the text field for reefer information.
Address preallocation based on the mode of transport
The Ship from and Ship to addresses are removed from the order or emptied again by selecting them in the Transport type field.
1. No preallocation is made for Merchants Haulage since the forwarder is rsponsible for the pre- or on-carriage.
2. For mode of transport Carrier/Merchant and Carrier/Carrier, the address Ship from (Empty container positiong) is filled with the pickup address from the Container tab of the goods description (eawarecont_t) from the order.
If this address has not been filled, the order address with classification PUP is pre-assigned instead.
If this address is not filled and this classification does not exist, the preallocation is made through classification SHP.
3. For mode of transport Merchant/Carrier and Carrier/Carrier, the address Ship to is filled with thea ddress with classificatino DEL from the order.
If this address is not filled and if this classification does not exist, the preallocation is made through classification CNE.
The preallocation of address fields in the booking is triggered once you change the mode of transport.
Accept addresses from the container in the order into the booking
If you are working with the address object in the container (global_sett_t: WBADRCONT = J), the addresses from the container object with qualifier PUP (Ship from) and DEL (Ship to) incl. reference and loading/delivery date in the oceanbooking are pre-assigned, provided that the booking was created with service type [Carriers Haulage] from an order.
If these addresses are not recorded in the container, the addresses with qualifier PUP and DEL from the order or qualifier SHP and CNE from the order are used instead.