| Aura panel | ||||
|---|---|---|---|---|
| ||||
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
The following basic data settings are necessary to be able to use this interface. |
Contents
| Table of Contents |
|---|
Function in the order
ADDRESSES → Address tab → EDI references sub tab
Assign Dakosy participant codes to the branch
Every branch receives its own Dakosy code.
This code must be assigned to the branch address to enable the transmission.
This entry is made in the address that is assigned to the branch.
→ This address is entered in the Forwarder field in every booking.
1. Determine the branch address:
2. Assign the Dakosy participant code to the branch address:
Open the address via ADDRESSES → ADDRESSES.
The DAKOSY code with qualifier OCBKG is entered on the EDI references sub tab:
3. The interface transmits the participant code from the Forwarders address.
In OceanBooking, in the Addresses sub-tab, in the Forwarder field, the named branch address is preassigned.
Branch address in the booking:
ORDER → SCAC CODES
Enter the Dakosy carrier code
The carrier code is assigned by Dakosy.
Fill the field Carrier code in the SCAC codes:
The carrier code is transmitted along with the booking. Dakosy thus assigns the booking to the correct carrier.
Current carrier codes are displayed in SCAC codes in ORDER.
Please enter the SCAC code upon booking entry - this is used to determine the carrier code.
ADDRESSES → Address tab → Input sub tab
SCAC code and location of the carrier
The SCAC code must be recorded in the address so that it can be pre-assigned upon selection of a carrier in the booking.
The SCAC code is entered in all office addresses of the carrier, i.e. Hamburg, Bremen, etc.
A SCAC code is recorded in ADDRESSES on the Input sub tab → field SCAC code per branch of the carrier.
Please make sure that the Location code is entered in the carrier address. → This location is transmitted as Booking Office and is required by many carriers.
ADMIN → NUMBER RANGES
Number range for data exchange already exists
Number ranges are also used for the ocean booking data transfer.
The creation of number ranges for data transfer is done automatically when CargoSoft is updated.
The data exchange requires the number ranges DAKBOOKEXCHANGE and DAKBOOKSEND.
They are automatically installed along with the update.
Create number range for ocean booking
The ocean booking number
One booking number can be set per branch.
A CargoSoft booking number is assigned for each new booking.
For file independent booking, this is a combination of the branch and a number, e.g. BRE1234.
The prefix for the branch is automatically determined by the system from the master data of the branch.
The number can be configured for each branch.
If no number is defined per branch, the system automatically determines a consecutive system number.
This number is consecutive for all bookings in the system!
COMPANY → BRANCHES
Assign the number range
A booking number can be configured per branch.
Enter the number range in the field Number range seafreight booking on the Number range tab.
When creating a booking from the order, the booking number consists of the file number and a sequence number that is added with an underscore character.
ADMIN → STATUS TYPES → STATUS EVENTS
Prepare status events
Each processing step of the booking is assigned a status. These are among others new creation, sent and system confirmations. The possible events are delivered with an update.
The provider in the status events is OCEANBOOK.
Notification by email
To receive an email upon occurence of an event, activate the checkbox Info to user.
The user (last change to the booking) receives an email if Send internal mails to email system has been activated in the employee options.
If a new ocean booking is linked to a file, the responsible person entered in the file can also receive notifications by email, in addition to the user.
Activate the checkbox Mail to resp. login.
.
Status INTERFACE ERROR
If the carriers report a status that is not (yet) available in the status events or if the interface identifies a problem, the status in the booking is set to INTERFACE ERROR.
The message shows the reported type and perhaps an information text.
ADMIN → STATUS TYPES → STATUS EVENTS
Status responses from carrier
The carriers return status messages for the bookings → these statuses concern the goods transport.
The relevant provider in the status events is OCEANSTAT.
Since carriers use different status messages, these are mapped with a standardized status by CargoSoft (Dakosy).
The Status types are available in the master data program Status events.
.
.
These statuses can be displayed in the CargoSoft file on the Status tab.
The status messages are displayed if the booking number and SCAC code are recorded in the order on the Statistics tab.
ADMIN → STATUS TYPES → STATUS EVENTS → Status types tab → Lower section per status type
Set Filling rule
In the lower section filling rules can be defined per status type.
In ADMIN → STATUS TYPES → Status types tab filling rule 22-ocean booking sent is available. This fill rule can be used for individual status types.
Required field Status type with search option for Filling rules:
.
Required field Fills field with search option FillsFieldCodes/Qualifier:
.
Fills field rule
.
Status tab in the order
With the first DAKOSY ACCEPTED - feedback the status is automatically set in the file (Status tab).
ORDER → PACKAGING CODES
Along with the transmission of the goods description, the UN code UN packaging type recorded in the Packaging codes in ORDER is transmitted as well.
→ The container ISO code must be entered in CONTAINER packaging codes.
| Info |
|---|
If this field is not filled, the code used in CargoSoft is transmitted instead. This may lead to errors. |