DTM Decoder

Key point

UN/EDIFACT DTM dates and times

A DTM value means nothing without its format code, and most codes carry no offset. A value with no offset is a local time at a place the value does not name. It is not UTC.

Paste a UN/EDIFACT DTM segment, or type a value and its format code (data element 2379). The tool takes the value apart field by field, says what it states, and reads an offsetless value in the zones you choose. A value means nothing without its code, and most codes carry no offset. The tool calls classifyEdifactDtmFormat on the code, then the parser of the kind that came back, and everything on the page is what those calls returned.

1. Paste a segment or a value

Segment or valueFormat code (2379)

A local time at a place the value does not name. The strip reads it in four example zones; none is the answer until you know where the sender's clock was. Change them.

A local time at a place the value does not name. The strip reads it in four example zones; none is the answer until you know where the sender's clock was. Change them.

The release character ? guards the +, so the element value is 202406151430+00. A signed hour is an offset, and the value names one instant.

The three characters UTC are read as an offset of +00:00, so the value names one instant. The formatter writes that offset as +00 and never as UTC. The field holds a signed hour, UTC or GMT and nothing else.

GMT is read as an offset of +00:00, like UTC: UN/ECE Recommendation 7 calls UTC formerly known as Greenwich Mean Time. The value names one instant. The formatter writes +00 and never GMT.

Code 205 ends in a signed HHMM offset from UTC, so the value names one instant and states the offset in force.

Code 208 ends in seconds and a signed HHMM offset from UTC. Use it to send seconds with an offset: the value names one instant and states the offset in force.

A date alone, in the form CCYYMMDD. It names no instant in any zone.

A time of day with seconds and no date. It names no instant: it is on no day.

A period is sent as two dates, one straight after the other, with no hyphen between them. The result holds the start and the end.

A period of two local date-times, one straight after the other. The code states no offset, so the strip reads both ends in four example zones. The zones are the example's picks: change them.

The field of code 303 holds a signed hour, UTC or GMT. CET is a zone abbreviation, and no standard maps an abbreviation to an offset, so the library returns the sentinel.

Code 101 has a two-digit year, and no standard says which century it belongs to. The EDI functions do not read it, so the library returns the sentinel. The pattern parsers read the same digits with a yearWindow that states the century.

Read as a segment: function qualifier 137, shown as sent and not interpreted; value 2222222222222222222222222222222222222222222222222222222222222222; format code 719. Text after the first composite is not read.

2. What the value states

DTMsegment+137qualifier:202406151430202406201600value:719format'start2024CCYY06MM15DDdate14HH30MMtimeend2024CCYY06MM20DDdate16HH00MMtimeno offset  

DTMsegment+137qualifier:20240615143045+0200value:208format'2024CCYY06MM15DDdate14HH30MM45SStime+0200ZHHMMoffset

No result

Code 201 has a two-digit year. No standard says which century it belongs to, so the EDI functions do not read it. Read it with parseDateWithPattern or parseDateTimeWithPattern: the pattern yyMMddHHmm and a yearWindow, which states the century you choose.

classifyEdifactDtmFormat("208")
parseEdifactOffsetDateTime("20240615143045+0200", "208")
toOffsetInstant("2024-06-15T14:30:45+02:00")

Offset: not stated

Offset: stated (+02:00)

The value names one instant.

A local time at a place the value does not name. It is not UTC.

A date. A date alone names no instant in any zone.

A time of day with no date and no offset: it is on no day.

A period of dates: a start and an end. The code states no offset, so neither end names an instant.

A period: a start and an end, each a local time. The code states no offset, so neither end names an instant until you choose a zone.

Kind

no result

Value

no result

Period end

no result

Instant

no result

Offset

no result

 

{ kind: "offsetDateTime", format: "208" } "2024-06-15T14:30:45+02:00" { instant: "2024-06-15T12:30:45Z", offset: "+02:00" }

3. Where an offsetless value lands

The value states no offset. Each zone below is a pick, from the example or from you, and not something the value says: the same digits, read there. Every row uses resolveLocal with disambiguation: "reject", so a time the clock shows twice or never is not resolved.

The value states no offset. Each zone below is a pick, from the example or from you. A row reads the start and the end there with resolveLocal and disambiguation: "reject", so a time the clock shows twice or never is not resolved.

The value states its offset, so there is nothing to choose.

A date or a time alone names no instant in any zone.

A period of dates names no instant: a date has no time of day to place.

No value.

Widest gap: 26 h, between Zonename/Wwwwwwwwwwwwwwwwwwwww and Zonename/Wwwwwwwwwwwwwwwwwwwww

Choose two zones to see how far apart the answers are.

ZoneInstantOffsetAs 205

1No zoneUTCAmerica/New_YorkAmerica/ChicagoAmerica/DenverAmerica/Los_AngelesEurope/LondonEurope/ParisEurope/BerlinEurope/MoscowAsia/TokyoAsia/ShanghaiAsia/KolkataAsia/DubaiAustralia/SydneyAustralia/AdelaidePacific/AucklandPacific/HonoluluAfrica/CairoAfrica/LagosAfrica/JohannesburgEurope/AmsterdamAsia/SingaporeAmerica/Atikokan

2No zoneUTCAmerica/New_YorkAmerica/ChicagoAmerica/DenverAmerica/Los_AngelesEurope/LondonEurope/ParisEurope/BerlinEurope/MoscowAsia/TokyoAsia/ShanghaiAsia/KolkataAsia/DubaiAustralia/SydneyAustralia/AdelaidePacific/AucklandPacific/HonoluluAfrica/CairoAfrica/LagosAfrica/JohannesburgEurope/AmsterdamAsia/SingaporeAmerica/Atikokan

3No zoneUTCAmerica/New_YorkAmerica/ChicagoAmerica/DenverAmerica/Los_AngelesEurope/LondonEurope/ParisEurope/BerlinEurope/MoscowAsia/TokyoAsia/ShanghaiAsia/KolkataAsia/DubaiAustralia/SydneyAustralia/AdelaidePacific/AucklandPacific/HonoluluAfrica/CairoAfrica/LagosAfrica/JohannesburgEurope/AmsterdamAsia/SingaporeAmerica/Atikokan

4No zoneUTCAmerica/New_YorkAmerica/ChicagoAmerica/DenverAmerica/Los_AngelesEurope/LondonEurope/ParisEurope/BerlinEurope/MoscowAsia/TokyoAsia/ShanghaiAsia/KolkataAsia/DubaiAustralia/SydneyAustralia/AdelaidePacific/AucklandPacific/HonoluluAfrica/CairoAfrica/LagosAfrica/JohannesburgEurope/AmsterdamAsia/SingaporeAmerica/Atikokan

No result

Zonename/Wwwwwwwwwwwww: The 01:30 time happens twice in Zonename/Wwwwwwwwwwwww on that date. With disambiguation: "reject", resolveLocal does not pick one.

Zonename/Wwwwwwwwwwwww: The 01:30 time happens twice in Zonename/Wwwwwwwwwwwww on that date. With disambiguation: "reject", resolveLocal does not pick one.

resolveLocal("2024-06-15T14:30:00", "Zonename/Wwwwwwwwwwwwwwwwwwwww", { disambiguation: "reject" })

"2024-06-15T18:30:00Z"

4. Written back by the matching formatter

 

formatEdifactDateTimePeriod("2024-06-15T14:30:00", "2024-06-20T16:00:00", "719")

A period is written without a hyphen. This is the element value. In an interchange, + is sent as ?+.

formatEdifactOffsetDateTime writes a zone as ±HH and never as UTC or GMT. This is the element value. In an interchange, + is sent as ?+.

How a segment is split. The tool splits a segment with the UN/EDIFACT default service characters and reads the three components of the DTM composite. The function qualifier is shown as sent and never interpreted. A custom UNA service string is not read. Only a segment is un-released: a bare value reaches the library as typed, so a ? left in it is refused, and the reason says so.

The two verdicts. The offset is stated, as with 205, 208 or a 303 value ending in +02, UTC or GMT: the tool shows the instant. Or the offset is not stated, as with 203, a date, a time or a period: the tool shows where the value lands in the zones you pick. A value or a code the library does not read shows NO SIGNAL with one sentence saying why. A CET under 303 is that, because the field holds a signed hour, UTC or GMT. A two-digit-year code is that too, and the sentence points at the pattern parsers with a yearWindow.

Why the zones are yours. The library maps no place to a zone, so the four zones are your picks. The 203 and CET presets open with four example zones, and the value does not say any of them. Each row calls resolveLocal with disambiguation: "reject": a time the clock shows twice, or never, is not resolved, and the row says why.

The functions. There is one parser, one formatter and one validator for each kind of value: parseEdifactDateTime and parseEdifactOffsetDateTime are two of the six. The matching formatter writes the value back, isValidEdifactDtmFormat tells an unknown code from a bad value, and resolveLocal turns a local time into an instant in a zone you name. The rules are in Intermodal: EDI Timestamps.

Worth trying: a CET value — the result is NO SIGNAL, and the sentence says the 303 field holds a signed hour, UTC or GMT. Replace CET with UTC and the value states its offset. Then a two-digit year — the result is NO SIGNAL: no EDI function reads a two-digit year, and the sentence names the pattern parser and the yearWindow that read it. For a value that returns a result, try a period of local date-times: each end lands in the zones you chose.