![]() |
![]() |
This option allows you to add the header details of a bill in the bill section of the manifest using SaudiEDI application.
To add the bill header details
1. Open the Bill Header page. (SAUDIEDI>> Manifest>> Create>> Bill>> Header)
Bill Header Details page
2. Enter information in Header Details fields.
Field | Description |
Bill Number | Enter the bill number. |
Bill Type | Select the bill type from the drop down list. |
Country of Origin | Enter
the country of origin or select the country using the ![]() |
Port of Loading | Enter
the port of loading or select the port using the ![]() |
Port of Loading Type | Select the port of loading type from the drop down list. |
Final Destination | Enter
the final destination or select the final destination using the
![]() |
Final Destination Port Type | Select the final destination port type from the drop down list. |
Shipment Type | Select the shipment type from the drop down list. |
Line ID | Enter the line ID which specifies the shipping line that carries the cargo. |
Total Weight | Enter the total weight of goods in bill of lading. |
No. of Packages | Enter the total number of packages in bill of lading. |
Total Containers | Enter the total number of containers in bill of lading. |
Total No. of Line Items | Enter the total number of line items in bill of lading |
Arabic Description | Enter the description of goods in Arabic. |
Remarks | Enter the remarks. |
Validation Rules for Bill Header
1. B/L type must be in the list specified in the message specification.
2. If manifest type is ‘Import’, B/L type must be ‘import’ or ‘transshipment import’.
3. If manifest type is ‘Export’, B/L type must be ‘export’ or ‘transshipment export’.
4. If
manifest type is ‘Transshipment Import’, B/L type must be ‘transshipment
import’.
5. If
manifest type is ‘Transshipment Export’, B/L type must be ‘transshipment
export’.
6. Storage location must be in the list specified in the message specification.
7. Port of loading must be a valid UNLOCODE code.
8. Port of loading type must be a valid UNLOCODE type.
9. Country of origin must be a valid ISO-3166 code.
10. Final destination must be a valid UNLOCODE code.
11. Final destination type must be a valid UNLOCODE type.
12. Shipment type must be in the list specified in the message specification.
13. If shipment type is ‘1 – FCL’, ‘5 – Many Containers shared among different Bs/L’
· Total number of containers must be > 0.
· Total number of line items must be >= Total number of containers
14. If shipment type is ‘2 – LCL’, ‘3 – PCL’:
· Total number of containers must be = 1
15. If
shipment type is ‘4 – No container’, ‘6 – Vehicles’, ‘9 – Direct discharge
shipment’:
· Total number of containers must be = 0.
16. If shipment type is ‘8 – Empty containers’:
17. Total number of line items must be = total number of containers
18. Total
number of containers declared must be equals to the number of container
records attached to the BL.
19. The
shipment type of the container linked to the item must be = shipment type
of
the BL.
20. Total weight declared in the B/L must be == ∑(item gross weight)
21. Total
number of packages declared in the B/L must be == ∑(item number of
packages)
22. Total number of items declared in the B/L must be = total number item records.
23. For bills which only contain cars, shipment type must be vehicle
24. For
bill not only contains cars, shipment type must be FCL, LCL, PCL or Many
container many BL.
25. Manifest
status must be match predefine range of values (this is in case the B/L
agent submission, and manifest status
should be ‘WAT’)
26. Port
Type for Port of discharge must be in the list specify in our Manifest
Message Specification.
27. Port of discharge must be a valid UNLOCODE.
Back to:
|