Every
document has to start with the following lines:
<?xml version="1.0"?>
<!DOCTYPE Interface SYSTEM "interface-v1-2.dtd">
The first line tells programs, which will automatically process this message, that this is a XML document. The second line makes the connection between this XML document and the DTD, where RSI defined the message format.
Content:
2.
and / or
Example:
<Interface>
<Header> DATA </Header>
<Shipment> DATA </Shipment>
.
.
.
<Shipment> DATA </Shipment>
<TrackingEvent> DATA </TrackingEvent>
.
.
.
<TrackingEvent> DATA </TrackingEvent>
<Shipment> DATA </Shipment>
.
.
.
<Shipment> DATA </Shipment>
<TrackingEvent> DATA </TrackingEvent>
.
.
.
<TrackingEvent> DATA </TrackingEvent>
.
.
.
</Interface>
Description:
Container for
the whole message. A message can contain several shipments and tracking events
in any order.
Parents: none
Content:
Example:
<Header>
<Sender> DATA </Sender>
<Receiver> DATA </Receiver>
.
.
.
<Receiver> DATA </Receiver>
<MessageId> DATA </MessageId>
</Header>
Description:
Container for
header data. The data in this container gives information about the Sender, one
or more Receiver(s) and a Message Identification.
Parents:
Content:
Example:
<Sender>
<CommunicationId> DATA </CommunicationId>
<Ref> DATA </Ref>
.
.
.
<Ref> DATA </Ref>
<Timestamp> DATA </Timestamp>
.
.
.
<Timestamp> DATA </Timestamp>
<Project> DATA </Project>
</Sender>
Description:
Container for
Sender data. The Communication Identification describes the branch office (3
characters branch office code + 3 characters city code; e.g. RSIDUS for Riege
Software International in Duesseldorf). Ref is an abbreviation for reference an
gives the possibility to transmit references according to the sender. In the
Timestamp (Date,Time,Minutes) segment, timestamps (format: CCYYMMDDHHMMSS)
specific to the sender can be transmitted.
The Timestamp
segment can be used with the following Types:
You can use the Ref segment without Type specification, if only one Reference is used. It will be stored as senders reference. If you have special references, please consult RSI, to define possible reference types. You can use the following reference types here:
Parents:
Content: Data,
length 6
Example:
<CommunicationId> RSIDUS </CommunicationId>
Description: The Communication Identification describes an branch office. It consists of 6 characters (3 characters branch office code + 3 characters city code). You have to ask RSI for suitable codes.
(It is very
important for us that the branch codes are unique.)
Parents:
Content: Data,
length 6
Example:
<Project> XMLTST </Project>
Description: This element can be used to transfer a project name.
Parents:
Content:
Example:
<Receiver>
<CommunicationId> DATA </CommunicationId>
<Ref> DATA </Ref>
.
.
.
<Ref> DATA </Ref>
<Timestamp> DATA </Timestamp>
.
.
.
<Timestamp> DATA </Timestamp>
<Project> DATA </Project>
</Receiver>
Description:
Container for
Receiver data. The Communication Identification describes the branch office (3
characters branch office code + 3 characters city code; e.g. RSIDUS for Riege
Software International in Duesseldorf). Ref is an abbreviation for reference an
gives the possibility to transmit references according to the receiver. In the
Timestamp (Date,Time,Minutes) segment, timestamps specific to the receiver can
be transmitted.
The Timestamp
segment can be used with the following Types:
You can use the Ref segment without Type specification, if only one Reference is used. It will be stored as senders reference. If you have special references, please consult RSI, to define possible reference types.
You can use
the following reference types here:
Parents:
Content: Data,
length 10, numeric
Example:
<MessageId> 1234567890 </MessageId>
Description: This element transfers a unique (per sending branch) message identification number (numeric!). It can be maximal 10 digits long. It is important that this number increases, which means that newer messages have higher numbers.
Parents:
Content:
2.
or
Example:
<Shipment>
<ShipmentId> DATA </ShipmentId>
<Shipper> DATA </Shipper>
<Consignee> DATA </Consignee>
<Notify> DATA </Notify>
.
.
.
<Notify> DATA </Notify>
<Goods> DATA </Goods>
<IncoTerms> DATA </IncoTerms>
<Tdt> DATA </Tdt>
<Charges> DATA </Charges>
<Values> DATA </Values>
.
.
.
<Values> DATA </Values>
<Ref> DATA </Ref>
.
.
.
<Ref> DATA </Ref>
<Eqd> DATA </Eqd>
.
.
.
<Eqd> DATA </Eqd>
<Timestamp> DATA </Timestamp>
.
.
.
<Timestamp> DATA </Timestamp>
<Ftx> DATA </Ftx>
</Shipment>
or if you want to delete a booking / shipment use the following structure:
<Shipment>
<ShipmentId> DATA </ShipmentId>
<DeleteFlag> delete </DeleteFlag>
</Shipment>
Description: Container for Shipment data.
The Timestamp
segment can be used with the following types:
You can use the following types in the Ref segment:
If you need other references, please contact RSI.
In the Ftx
segment
you can use the following types:
Parents:
Content:
Example:
<ShipmentId>
<UniqueId> RSIDUS00123456789 </UniqueId>
<Master> 020-12345678 </Master>
<House> DUS-12345678 </House>
<TransportType> air </TransportType>
<ShipmentType> master </ShipmentType>
</ShipmentId>
Description: Container
for Shipment Identification information, like a unique message identification,
master and house. The TransportType is used to specify, whether the shipment is air or sea
. The ShipmentType has the values booking,
house, master, direct
Parents:
Content: Data,
length 17
Example:
<UniqueId> RSIDUS00123456789 </UniqueId>
Description:
This is a unique identification of the shipment. This Id is build according to
the following rules: the first 6 character specify a branch code (3 branch
office name + 3 city code). You have to ask RSI for a suitable code to ensure
that a unique code is chosen. This branch code is same as in the Sender
element CommunicationId.
The next 11
digits can be a running number at the branch which increases. We suggest 2
digits for the year (in the example 00 for 2000) + 9 digits of a running number.
But you can
also use other numbers, which are unique referring to the sending branch.
Parents:
Content: Data,
length 12, conditional, depends on ShipmentType
Example:
<Master> 020-12345678 </Master>
Description: Master AWB/BL number.
Parents:
Content: Data,
length 12, conditional, depends on ShipmentType
Example:
<House> DUS-12345678 </House>
Description: House AWB/BL number.
Parents:
Content: fix
values: air
or
sea
Example:
<TransportType> air </TransportType>
Description:
This element shows the transport method of the shipment. It has the fix values air
or sea
Parents:
Content: fix
values: booking,
house, direct, master
Example:
<ShipmentType> booking </ShipmentType>
Description:
This element specifies the kind of shipment. It can contain the fix values booking,
house, direct or master
.
Please
notice, that the order in which this tpyes (over different messages) appear is
fix refering to the logical process of shipping. After a booking you can get a
house and a master, but not vice versa.
Parents:
Content: numeric
integer value, lenght 3, Example:
<NumberOfOriginals> 3 </NumberOfOriginals>
Description: This element specifies the number of originals (= regular master BL papers), which were printed. Used in Sea only.
Parents:
Content: fix
values: delete
Example:
<DeleteFlag> Delete </DeleteFlag>
Description: This element gives you the possibility to delete a shipment at the receivers system. If this element occurs not other data in the shipment container is transmitted, see example in Shipment
Parents:
Content:
Example:
<Shipper>
<AddressId> DATA </AddressId>
<Address> DATA </Address>
<AccountNo> DATA </AccountNo>
<Shipper>
Parents:
Content:
Example:
<AddressId>
<Data> DATA </Data>
<Type> DATA </Type>
</AddressId>
Description: Container for AddressId Data. It contains a Data and a Type element, which are pure text data. Use the Data element to store Address-Numbers etc. and the Type element to specify the kind of Address.
You can use
the following Types:
Parents:
Content: Data
and length depend on the container, this element is used in.
Example:
<Ref>
<Type> PON </Type>
<Data> PON4711 </Data>
</Ref>
.
.
.
<Timestamp>
<Data> 20000202111213 </Data> <!-- Date/Time: 02.02.2000 at 11:12:13 -->
</Timestamp>
Description: This
element is used in several places throughout the message and contains pure
character and/or numeric data. In many cases in the parent container of this Data element
is a Type
element specified, which gives this data a
special meaning. Sometimes its content only depends on the parent container.
Parents:
Content: Data,
Type depends on the context it is used. Fix values as agreed with RSI.
Example:
<Timestamp>
.
<Type> ETA </Type>
.
</Timestamp>
Description: This
element is used in several places throughout the message. It is used to specify
a kind of qualifier which tells something about the meaning of the Data
element. The concrete type-value depends on its
context and is defined there.
Parents:
Content:
Example:
<Address>
<Name> DATA </Name>
.
<Name> DATA </Name>
<Street> DATA </Street>
.
<Street> DATA </Street>
<City> DATA </City>
<Country> DATA </City>
</Address>
Description: Container for Address Data. The elements Name and Street must appear once and can repeated up to three times. City and Country must appear once.
Parents:
Content: data,
length: 35, element can be repeated 3 times
Example:
<Name> Riege Software International GmbH</Name>
<Name> Headquarter </Name>
Description: This element contains the name information of an address. It can be repeated up to three times.
Parents:
Content: data,
length 35, element can be repeated 3 times
Example:
<Street> Mollsfeld 10 </Street>
<Street> 0th Floor </Street>
Description This element contains the street information of an address. It can be repeated up to 3 times
Parents:
Content:
Example:
<City>
<CityName> Duesseldorf </CityName>
<Zip> 40222 </Zip>
<State> NRW </State>
<CityCode> DUS </CityCode>
</City>
Description This element is a container for city information.
Parents:
Content: data,
length 35
Example:
<CityName> Duesseldorf </CityName>
Description: This element contains the city name of an address.
Parents:
Content: data,
length: 9
Example
<Zip> 40222 </Zip>
Description: This element contains the Zip Code of a City.
Parents:
Content: data,
length 9
Example:
<State> NRW </State>
Description: This element contains the State/Province of a city.
Parents:
Content: data,
length 5
Example:
<CityCode> DUS </CityCode>
Description: This element contains the Three/Five (air/sea) letter code of a city. The three letter codes (air) refer to the IATA standard codes. The five letter codes follow the UN/LOCODES city codes.
Parents:
Content:
Example:
<Country>
<CountryName> Germany </CountryName>
<CountryIsoCode> DE </CountryIsoCode>
</Country>
Description: This
element is used as a container for CountryName
and CountryIsoCode.
Parents:
Content: data,
length: 40
Example: Country
Description:
This
element contains the name of a country.
Parents:
Content: data,
length: 2
Example: Country
Description:
This
element contains the 2 character UN ISO SO 3166 alpha 2 codes for the countries.
Parents:
Content: data,
length 16
Example:
<AccountNo> 1234567890-12345 </AccountNo>
Description: This element is used to transfer an Account number.
Parents:
Content:
Example:
<Consignee>
<AddressId> DATA </AddressId>
<Address> DATA </Address>
<AccountNo> DATA </AccountNo>
<Consignee>
Description: Container for the consignee address.
Parents:
Parents:
Content:
Example:
<Notify>
<AddressId> DATA </AddressId>
<Address> DATA </Address>
<AccountNo> DATA </AccountNo>
<Notify>
Description: Container for additional addresses, e.g. Notify addresses. With the optional Type element, you can specify the kind of address transmitted. Allowed types are:
Parents:
Content: data,
length 3
Example:
<IncoTerms>
<Type> CFR </Type>
<Data> Cost and Freight </Data>
</IncoTerms>
Description: Container for the Inco Terms of a shipment. The Type is defined below. In the data element you can give a description of the term.
Possible
values for the type element with description (can be used in the Data element):
Parents:
Content:
3.
and/or
Example:
<Tdt>
<Departure> DATA </Departure>
<Destination> DATA </Destination>
<Air> DATA </Air>
</Tdt>
Description: Container with the transport details of a shipment.
Parents:
Content:
Example:
<Departure>
<CityCode> JFK </CityCode>
<CityName> New York </CityName>
</Departure>
Description: This element is a container for the Three/Five letter code of an air/sea port and a city name, which is optional. The element describes the origin of a flight or transport.
Parents:
Content:
Example:
<Destination>
<CityCode> LHR </CityCode>
<CityName> London Heathrow </CityName>
</Destination>
Description: This element is a container for the Three/Five letter code of an air/sea port and a city name, which is optional. The element describes the origin of a flight or transport.
Parents:
Content:
Example:
<Loading>
<CityCode> DEHAM </CityCode>
<CityName> Hamburg </CityName>
</Loading>
Description: This element is a container for the Three/Five letter code of an sea port of loading and its city name, which is optional. The element occurs only in a Sea Tdt container.
Parents:
Content:
Example:
<Discharge>
<CityCode> DEHAM </CityCode>
<CityName> Hamburg </CityName>
</Discharge>
Description: This element is a container for the Three/Five letter code of an sea port of discharge and its city name, which is optional. The element occurs only in a Sea Tdt container.
Parents:
Content:
Example
<Air>
<Departure> DATA </Departure>
<Destination> DATA </Destination>
<FlightId> DATA </FlightId>
<Carrier> DATA </Carrier>
</Air>
Description: This element is a container for Flight details like the optional elements Departure and Destination, a flight identification segment, an optional carrier and optional (none, one or more) data/time information.
Parents:
Content:
Example:
<FlightId>
<CarrierCode> DATA </CarrierCode>
<FlightNo> DATA </FlightNo>
<Timestamp> DATA </Timestamp>
</FlightId>
Description: This element is used as container for the identification of a flight.
Parents:
Content: data,
length: 3
Example:
<CarrierCode> LH </CarrierCode>
Description: This element contains the carrier code (IATA Standard) of an airline.
Parent
Content: data,
length: 6
Example:
<FlightNo> 4711 </FlightNo>
Description: This element contains the flight number.
Parents:
Content:
Example:
<Carrier>
<AddressId> DATA </AddressId>
<Address> DATA </Address>
</Carrier>
Description: This container holds information about a carrier like address information.
Parents:
Content:
Example:
<Sea>
<Loading> DATA </Loading>
<Discharge> DATA </Discharge>
<VesselId> DATA </VesselId>
<Carrier> DATA </Carrier>
</Sea>
Description: This container holds special information about a sea transport details, like the port of loading, the port of discharge and an optional carrier.
Parents:
Content:
Example:
<VesselId>
<VesselName> DATA </VesselName>
<VoyageNo> DATA </VoyageNo>
</VesselId>
Description: This is a container for the identification of a vessel. It stores the name of the vessel and a voyage number.
Parents:
Content: character
data, length: 35
Example:
<VesselName> MS Europe </VesselName>
Description: This element contains the name of the vessel.
Parents:
Content: character
data, length: 17
Example:
<VoyageNo> SNL-HKG-HAM-123 </VoyageNo>
Description: This element contains the voyage number.
Parents:
Content:
Example:
<Goods>
<Description> DATA </Description>
<Gid> DATA </Gid>
</Goods>
Description: This element is a container for goods information. It contains the Nature of Goods (Description) and detailed information about single goods items in the (Gid) segment.
Parents:
Content:
Example:
<Description> 2 Items not restricted chemicals </Description>
Description: This element contains the nature of goods information.
Parents:
Content:
Example:
<Details>
<Pieces> DATA </Pieces>
<Length> DATA </Length>
<Height> DATA </Height>
<Width> DATA </Width>
<Unit> DATA </Unit>
<PackingType> DATA </PackingType>
<Mea> DATA </Mea>
<Vol> DATA </Vol>
</Details>
Description: Container for details of a single goods item data.
This segment
can be repeated within the Gid segment. You have the possibility to specify
details to the good item like this: e.g. the Gid element exists of 10 pieces X,
than you can use 2 Details segments to specify, that 6 pieces are Y and 4 pieces
are Z. Please use CM (centimeter) as Unit for length, width and height.
Parents:
Content: numeric
value, length 4
Example:
<Length> 123 </Length>
Description: This element contains the Length in centimeter (CM).
Parents:
Content: numeric
value, length 4
Example:
<Height> 123 </Height>
Description: This element contains the Height in centimeter (CM).
Parents:
Content: numeric
value, length 4
Example:
<Width> 123 </Width>
Description: This element contains the Width in CM.
Parents:
Content:
Example:
<PackingType>
<Type> Cases </Type>
</PackingType>
Description: This element describes the packing type, e.g. cases, palette, container, box, ...). It is mandatory to specify a unique qualifier. An optional description can be sent in the data segment. Ask RSI for suitable qualifier, if you need this segment.
Parents:
Content: character
data, length: 3, fix values: defined where used.
Example:
<Unit> CBM </Unit>
Description: This element gives information about the unit of numeric values like in weights, dimensions, volumes. See there for allowed values.
Parents:
Content:
Example:
<Vol>
<Data> 123456789.00 </Data>
<Unit> CBM </Unit>
</Vol>
Description: This element contains the volume in cubic meters (CBM).
Please use
cubic meters CBM
as
Unit.
Parents:
Content:
Example:
<Mea>
<Type> GRS </Type>
<Data> 123456.00 </Data>
<Unit> KGM </Unit>
</Mea>
Description: This element contains measurements like gross weight, chargeable weight, etc.
Type can have
the following qualifiers:
Unit can have the following values:
Parents:
Content:
Example:
<Gid>
<Pieces> 12345 </Pieces>
<Vol> DATA </Vol>
<Mea> DATA </Mea>
.
<Mea> DATA </Mea>
<RateClass> DATA </RateClass>
<Rate> DATA </Rate>
<CommodityItemNo> DATA </CommodityItemNo>
<Ftx> DATA </Ftx>
.
<Ftx> DATA </Ftx>
<Label> DATA </Label>
<Details> DATA </Details>
<Gid>
Description: This element is used as container for single goods item information.
The Ftx
element is unused in this version!
Parents:
Content: numeric
value, length 5
Example:
<Pieces> 12345 </Pieces>
Description: This element identifies the number of pieces.
Parents:
Content: character
data, length: 1
Example:
<RateClass> M </RateClass>
Description: This element specifies the rate class.
Parents:
Content:
Example:
<Rate>
<Data> 12.00 </Data>
<Cur> DEM </Cur>
</Rate>
Description: In this element you can specify a rate value according to the rate, e.g. 12.00 DEM pro kgm chargeable weight.
Parents:
Content:
Example:
<WeightCharge>
<Data> 123456.00 </Data>
<Cur> DEM </Cur>
</WeightCharge>
Description: This element contains the weight charge of the goods item.
Parents:
Content: character
data, length 7
Example:
<CommodityItemNo> 1 </CommodityItemNo>
Description: This element specifies the commodity item number.
Parents:
Content: character/numeric
data, length 35
Example:
<Label> ADE24214515 </Label>
Description: This element specifies a label of the Gid item.
Parents:
Content:
Description: This is a container for the charges.
If you need
the charges container, please contact RSI to specify suitable types.
The Type
segment in the Ftx segment can be free or filled with "Charges".
Parents:
Content: character
data, length 3
Example:
<Cur> USD </Cur>
Description: This element contains the currency.
Parents:
Content: character
data, length 1, values: P or C
Example:
<Terms> P </Terms>
Description: This element contains the delivery terms. (P=Prepaid C=Collect)
Parents:
Content: character
data, length 1, values: A or C
Example:
<Due> A </Due>
Description: This element indicates, whether the charge is paid due carrier or due agent.
Parents:
Content:
Example:
<Values>
<Type> insurance </Type>
<Data> 1000.00 </Data>
<Cur> USD </Cur>
<Notify>
Description: This element is used to transmit several kinds of values as specified below in the possible types definition. The data segment is used to store the value referring to the type. The cur segment shows the Currency of the value in the data.
Possible
types for airfreight are:
Parents:
Content:
Example:
<Dgs> </Dgs>
.
or
.
<Dgs>
<DgsHazardCode> 3.1 </DgsHazardCode>
<DgsHazardPage> A17-4 </DgsHazardPage>
<DgsUndg> 4 </DgsUndg>
<DgsFlashPoint> 35.0 </DgsFlashPoint>
<DgsShipmentFlashPoint> 37.2 </DgsShipmentFlashPoint>
<DgsFlashQualifier> CEL </DgsFlashQualifier>
<DgsPackingGroupCode> II </DgsPackingGroupCode>
<DgsEmsNo> 174 </DgsEmsNo>
<DgsMfagNo> 21 </DgsMfagNo>
<DgsTremNo> 42128-7 </DgsTremNo>
<DgsHazardIdUp> 1200 </DgsHazardIdUp>
<DgsHazardIdLow> 3400 </DgsHazardIdLow>
<DgsLabel> FIRE </DgsLabel>
<DgsInstractCode> 127 </DgsInstractCode>
<DgsTransportCategory> CAR </DgsTransportCategory>
<DgsTransportPermission> SST </DgsTransportPermission>
</Dgs>
Description: This
container is optional inside the shipment container and is used to qualify
dangerous goods. All elements inside this container are optional. This gives you
the possibility to use this container as a kind of flag, which means, if you
send an empty Dgs container,
this is interpreted as "Shipment contains dangerous goods", even
though they are not further specified.
Parents:
Content: character
data, length 3
Example:
<DgsRegulations> IMD </DgsRegulations>
Description: Specify the dangerous goods regulations here.
Parents:
Content: character
data, length 7
Example:
<DgsHazardCode> 3.1 </DgsHazardCode>
Description: Specifies hazard code
Parents:
Content: character
data, length 7 Example:
<DgsHazardPage> A17-4 </DgsHazardPage>
Description: Specifies hazard page
Parents:
Content: numeric
data, length 4, 0 decimals Example:
<DgsUndg> 4 </DgsUndg>
Description: Specify the UNDG number here.
Parents:
Content: numeric
data, length 4, 1 decimals, xxxx.y
Example:
<DgsFlashPoint> 35.0 </DgsFlashPoint>
Description: Specify the flashpoint in degree celsius.
Parents:
Content: numeric
data, length 4, 1 decimal, xxxx.y
Example:
<DgsShipmentFlashPoint> 37.2 </DgsShipmentFlashPoint>
Description: Specify the flashpoint of the shipment in degree celsius. If you want/have to use another kind of measurement, please use the DgsFlashQualifier segment to specify it (e.g. if you want to use Fahrenheit)
Parents:
Content: character
data, length 3
Example:
<DgsFlashQualifier> CEL </DgsFlashQualifier>
Description: This element is used to specify the measurement of the flashpoint values. The default for the flashpoints are degree Celsius (CEL), so if you do not transmit this field, the receiving party interprets the flashpoint as Celsius. You can also specify Fahrenheit, qualifier "FAH".
Parents:
Content: character
data, length 3
Example:
<DgsPackingGroupCode> II </DgsPackingGroupCode>
Description: Specify the packing code.
Parents:
Content: numeric
data, length 6
Example:
<DgsEmsNo> 174 </DgsEmsNo>
Description: Specify the EMS number.
Parents:
Content: numeric
data, length 4
Example:
<DgsMfagNo> 21 </DgsMfagNo>
Description: Specifies the MFAG number
Parents:
Content: character
data, length 10
Example:
<DgsTremNo> 42128-7 </DgsTremNo>
Description: Specifies the TREM card number
Parents:
Content: character
data, length 4
Example:
<DgsHazardIdUp> 1200 </DgsHazardIdUp>
Description: Specifies the harard id number (up).
Parents:
Content: character
data, length 4
Example:
<DgsHazardIdLow> 3400 </DgsHazardIdLow>
Description: Specifies the hazard id number (down).
Parents:
Content: character
data, length 4
Example:
<DgsLabel> FIRE </DgsLabel>
Description: Specifies the label for the main risk.
Parents:
Content: character
data, length 3
Example:
<DgsInstractCode> 127 </DgsInstractCode>
Description: Specify the packing instruct code.
Parents:
Content: character
data, length 3
Example:
<DgsTransportCategory> CAR </DgsTransportCategory>
Description: Specifies the transport category.
Parents:
Content: character
data, length 3
Example:
<DgsTransportPermission> SST </DgsTransportPermission>
Description: Specifies the transport category.
Parents:
Content:
Example:
<Eqd>
<EqdType> CN </EqdType>
<EqdId> MAER 1724486 </EqdId>
<EqdSize; FLAT </EqdSize>
<SealNo> 1324K </SealNo>
</Eqd>
Description: This Element is a container for equipment details. It can be repeated within the Shipment container for different equipment information. In the EqdType element, you can specify the type of equipment. In this version we have only one type, CNT for containers. If you need other types, please ask us for suitable codes.
The EqdId
segment specifies an identifier for the equipment, e.q. an container
identification label.
The elements Pieces,
Mea and
Vol
refer
to the content of the equipment, e.g. the container. Ref .
Parents:
Content:
charater
data, length 3
Example:
<EqdType> CN </EqdType>
Description: This element specifies the type of the equipment. Possible values are:
Parents:
Content: character
data, length 15
Example:
<EqdSize> FLAT </EqdSize>
Description: This element contains the size/type of the equipment. Ask RSI for suitable codes.
Parents:
Content: character
data, length 17
Example:
<EqdId> MAER 47110815007 </EqdId>
Description: Specifies equipment identification.
Parents:
Content: character
data, length 10
Example:
<SealNo> 123474K </SealNo>
Description: Specifies the seal number
Parents:
Content:
Example:
<Ref>
<Type> PON </Type>
<Data> PA342984 </Data>
</Ref>
Description: This
Element is a container for references. The type has to be agreed with RSI.
Possible Type are specified in the parent elements of Ref
.
Parents:
Content:
Example:
<Timestamp>
<Type> ETA </Type>
<Data> 20000202112233 </Data>
</Timestamp>
Description: RSI uses something called timestamp to transfer Date and Time information. A timestamp is a numeric value which has the format CCYYMMDDHHMMSS, where CC=2 digits century, YY=2 digits year, MM=2 digits months DD=2 digits days, HH=2 digits hours, MM=2 digits minutes and SS= 2 digits seconds.
Parents:
Content:
Example:
<Ftx>
<Type> HAN </Type>
<Data> Handling Information </Data>
</Ftx>
Description: This element is used to transmit free text. It can also be used to transmit, e.g. handling information. Qualifier have to be specified.
Parents:
Content:
2.
or
Example:
<TrackingEvent>
<UniqueId> RSIDUS00987654321 </UniqueId>
<Type> DEP </Type>
<CityCode> DUS </CityCode>
<CityName> DUESSELDORF </CityName>
<Timestamp><Data> 20000322084900 </Data></Timestamp>
<Ftx><Data> Departed regular </Data></Ftx>
</TrackingEvent>
Description: This container exists of data about a tracking event. The unique identification connects the tracking event to a shipment.
The type of a
tracking event specifies the event itself, e.g. typical events are "booked
on flight", "arrived", "departed", "delivered to
forwarder", and so on. Because every software system uses its own codes for
this events, we have to do a mapping between the receiver and sender side, so we
suggest to ask RSI for the definition of codes which fits the needs of all
included parties.
The next two
elements specifies the city, the event took place. The three/five letter city
code qualifier is mandatory, the city name is optional.
The timestamp
element specifies the time the event occured.
Finally there
is a free text element, which can be used to transfer additional information to
this tracking event. For example if you have an event which has the meaning of
"Goods not delivered", you can use the Ftx
to
specify a reason, why it was not possible to deliver.
You do not
have to specify a type for the Ftx element, because it is unique within its context.
Parents: