Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : DPTDAMDOD001 - - (Claimant - Damage - Damaged object - données véhicule)
- Approved
, and is part of release 202001 |
Sender :
Receiver :
Status : 2 - Version : 3
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
|||||||
| 10 |
Claimant - Damage - Damaged vehicle
|
No
|
-
|
-
|
Mand.
|
DOD+001
|
ObjectDamagedTractorVehicle
|
||
| 20 |
Claimant - Damage - Damaged vehicle - object instance identifier
|
No
|
-
|
-
|
Option.
|
DOD+001+x--x:002/003
|
RiskObjectDetail ObjectIdentifier CodeListIdentifier
|
||
| 30 |
Claimant - Damage - Damaged vehicle - object instance name
|
No
|
-
|
-
|
Option.
|
DOD+001+:::x--x
|
RiskObjectDetail ObjectName
|
||
| 40 |
Claimant - Damage - Damaged vehicle - Marque / Modèle / Type
|
No
|
-
|
-
|
Option.
|
DOD+001 - NME+005+x--x:x--x:x--x
|
MakeModelTypeName NameDetail LastName FirstName
|
||
| 50 |
Claimant - Damage - Damaged vehicle - Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Option.
|
DOD+001 - RFF+010:x--x:001
|
RegistrationPlateReference
|
||
| 60 |
Claimant - Damage - Damaged vehicle - Véhicule immobilisé
|
Yes
|
1
|
Option.
|
DOD+001 - ATT+CP12+x--x
|
TheVehicleIsOutOfServiceCode
|
|||
| 70 | n |
Claimant - Damage - Damaged vehicle - Driver
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004
|
PartyDriver
|
|
| 80 | n |
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - Nom de famille
|
No
|
-
|
-
|
Cond.
|
Mandatory
|
DOD+001 - PTY+004 - NME+001+x--x
|
OfficialName NameDetail LastName
|
| 90 | n |
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - 1er prénom
|
No
|
-
|
-
|
Cond.
|
Mandatory
|
DOD+001 - PTY+004 - NME+001+:x--x
|
OfficialName NameDetail FirstName
|
| 100 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - rue
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+x--x
|
OfficialAddress AddressDetail StreetName
|
|
| 110 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+:x--x
|
OfficialAddress AddressDetail HouseNumber
|
|
| 120 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+::x--x
|
OfficialAddress AddressDetail BoxNumber
|
|
| 130 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - extension
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+::::x--x
|
OfficialAddress AddressDetail AddressExtension
|
|
| 140 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+:::::x--x
|
OfficialAddress AddressDetail AddressIdentifier
|
|
| 150 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+:::::x--x:x--x
|
OfficialAddress
|
|
| 160 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - code postal
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002++x--x
|
OfficialAddress PostalCode
|
|
| 170 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - localité
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002+++x--x
|
OfficialAddress CityName
|
|
| 180 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse - code pays
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - ADR+002++++x--x
|
OfficialAddress CountryCoded
|
|
| 190 | n |
Claimant - Damage - Damaged vehicle - Driver - Date de naissance
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - DTM+001:x--x:001
|
BirthDate
|
|
| 200 | n |
Claimant - Damage - Damaged vehicle - Driver - Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - COM+001:x--x
|
PrivateTelephoneCommID CommunicationChannelNumber
|
|
| 210 | n |
Claimant - Damage - Damaged vehicle - Driver - Numéro de fax
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - COM+002:x--x
|
FaxCommID CommunicationChannelNumber
|
|
| 220 | n |
Claimant - Damage - Damaged vehicle - Driver - Adresse boîte postale électronique
|
No
|
-
|
-
|
Option.
|
DOD+001 - PTY+004 - COM+003:x--x
|
EmailAddressCommID CommunicationChannelNumber
|
|
(*) n u d : new / updated / deleted since previous version.
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard. And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used". Ideally we should implement the same ideas.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.