...
Contents
Table of Contents |
---|
...
Fields on this tab
Field | Use | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
B/L form (=form code) | Selection of the B/L that is to be sent or printed. This code consists of the Shipping agents and the B/L code (for this traffic area, this service, etc.).
Side note: B/L name and form code in the FormGenThe following information need to be filled on the Instructions tabin order for Dakosy to identify the shipping agent/sipping company that the B/L ought to be forwarded to:
These details can/should ideally be recorded in the FormGen in every B/L that may be sent.. |
|
The search result shows that every shipping company has its own form code. | |
Side note: | The formatting rules for the transmission of B/L data differ from those to print a B/L. In the order, the user can select a vessel through the Dakosy sailing list. Select the shipping company/agent and the corresponding B/L for the service. In the example below, the correct B/L form is set in the B/L tab that matches the shipping data selected in the order → header data via the shipping list. Every B/L form has a number in Dakosy. In CS you can prepare a connection of the B/L form number with the shipping agent/shipping company code as a B/L template in the FormGen. The program automatically loads this B/L template in the order if all data match. The code can be selected freely in the FormGen. The code in the example is easy to identify for the processing of B/L data in the order. Entry from the sailing list in the order: |
---|
Vessel departure no. contains agent code: |
B/L data on the Instructions tab have the same agent code and B/L form no. from the basic data: |
B/L template in the FormGen has the corresponding code: |
HB/L number | Entry of the House B/L no.
The entry of the HB/L no. is transmitted to the Statistic tab in the order and vice versa. Info: Split into BL type XXX | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
OB/L number | Entry of the Ocean B/L number The entry of the OB/L no. is transmitted to the Statistic tab and vice versa. | |||||||||
OB/L booking no. | Booking no. for the shipping agent.
The entry of the OB/L booking no. is transmitted to the statistic tab and vice versa. | |||||||||
Shipping agent | Entry of the shipping agent's code to whom the B/L data are to be transmitted. B/Ls can only be transmitted to the agent through the B/L form types.
| |||||||||
Side note: | When printing/sending the B/L, all fields that were taken into account upon generation of the B/L in the form generator will also be printed/sent. From this mask you can also send the B/L data to the agent via the DAKOSY server. |
The combination of the 3 components forms the agent who creates and delivers the B/L. This code field shows your internal code.
If the agent is already linked to the vessel in the sailing list, the Shipping agent field on the Instructions tab is filled automatically. | ||
Contract no. | Entry of a contract number if agreements have been made with the shipping agent. | |
---|---|---|
Container no. | If an HB/L is linked to a consol container, the container number is entered into this field, which will be grayed out. The container number recorded on the Consolidation tab is automatically entered in the B/L tab → Instructions and is non-editable. | |
Seal number | If an HB/L is linked to a consol container, the seal no. from the Consolidation tab Seafreight is entered in this field, which will be grayed out. The seal no. recorded on the Consolidation tab is automatically entered in the B/L tab → Instructions and is non-editable. |
Precarriage by | Entry of the name or mode of transport of the Type of transport in ORDER. | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Ocean vessel | Entry of the vessel name.
| |||||||||
Voyage no. | Entry of the voyage number.
| |||||||||
All place names/ports consist of two fields for the entry of
| ||||||||||
Place of receipt,
| Entry of the place of receipt,
| |||||||||
Port of loading, | Entry of the port of loading
| |||||||||
Place of issue | Entry of the place of issue. The place of issue can be pre-assigned with values from the basic data. | |||||||||
Date of issue
| Entry of the date of issue.
|
|
Total no. of pkgs. | Entry of the total number of packages of the first level.
| |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Disbursements | Entry of disbursements To store the disbursements in the data container in the goods description, enter the currency code in the first field and the amount in the second field. The first field provides a search feature: search for currency codes. Double click into the field Disbursements to open the search mask. | |||||||||
Movement | Required field for the B/L transmission via INTTRA. Freely editable field → cannot be filled with values from the basic data. This field is neither pre-assigned with entries from Order → Statistic nor the basic data. | |||||||||
No. of original B/Ls | No. of original B/Ls that are to be issued. The number of original B/Ls can be filled with a default entry in the FormularGenerator, which will be pre-assigned in this field. → The spelling in this field is taken into account for the B/L print. | |||||||||
Freight payable at | Entry of the location or freight payability. A search feature is available. Search function with access to FREIGHT CODES in ORDER: |
Freight payable at
| Entry of the DAKOSY freight payability code. Select from:
Search for freight payability codes: double click into the first field Freight payable at. → This field is a Dakosy field only. |
---|
B/L transmission: Freight payable at in collect and prepaid shipmentsIn the case of a B/L transfer, if the Freight payable at code 'All charges collect' is used (recipient pays all costs door - door), all 6 charge codes are also transferred: TCC + 101035 ::: Inlandfreight origin: C' The same applies to all charges prepaid shipments. The 6 charge codes are also transmitted with the B/L-data. The codes are created with the update script in the basic data ORDER → FREIGHT CODES (fraco_t). |
Print parameters Originals/Copies | Entry for the internal print of originals and copies on the (internal) printer intended for the B/L print. The preallocation in this field comes from the form generator. |
---|---|
Print parameter for Crystal Reports only Type Draft | Select between Original, Original Layout, Express, Express Layout, if this is a Crystal Reports print. Activate the checkbox if you would like a draft. |
Login (for responses) Originals/Copies Type | Feedback from the carrier was previously only sent to the email address of the user who sent the B/L. If another user is specified in the B/L for the feedback in the Login field (eabl_t.fk_mitarb_login) the feedback will be sent to this user in the future. This field is pre-assigned automatically when you create or modify the port document or B/L. If the sending user is not the user entered in the Login field and if this field was not filled in manually, the system will issue a query, asking whether the login (with contact details) should be updated. Number of originals and copies that the shipping agent is to issue. Select between Original and Express B/L. |