Station (CI, Inbound)
- ser_hcskb_api
Field Descriptions
Field | Description | Type (Length) | Mandatory | Remark |
|---|---|---|---|---|
@type | Loading or unloading station | N4/10 | True | Values: loading, unloading |
name | Name (identification) of the station | C1/200 | False |
|
place_reference_id | Reference (identification) to the location | C1/200 | False | Can be used to map address data from master data |
company_name | Company name | C1/200 | False |
|
address | Street and number | C1/100 | False |
|
zip | Postal code | C1/20 | False |
|
city | City | C1/100 | False |
|
region | Region | C1/100 | False |
|
country_id | Country code | C1/2 | False | ISO 3166-1 alpha-2 |
loading_name | Shipper specific location or stop identifier | C1/50 | False |
|
loadingramp | Name of ramp/gate | C1/50 | False |
|
start | Loading/unloading period begin (date and time). | C1/19 | False | This a local timestamp. This means the offset on the timestamp is ignored and the time is always related the local location! Timezone for the location is defined in field timezone instead. Examples: Loading or unloading times for 2021-10-08T14:15:00Z, 2021-10-08T14:15:00+02:00 and even 2021-10-08T14:15:00-10:00 will be displayed in our front-end application as 14:15. The offsets for exports and further data processing is solely taken from the timezone field! |
end | Loading/unloading period end (date and time). | C1/19 | False | See description above |
timezone | Time zone of the loading / unloading location | C1/10 | False | Naming must follow tz database (also known as IANA time zone database) We only accept entries marked as “Canonical” in tz database. |
comment | Station comment | C1/3000 | False | This is free text. |