> Syntax independent - MCIs - Messages > Details

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 202201 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
Version : 4
Status : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2-UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
10  
Claimant - Damage - Damaged vehicle
No
-
-
Mand.
 
DOD+001 
20  
Claimant - Damage - Damaged vehicle - object instance identifier
No
-
-
Option.
 
DOD+001+x--x:002/003 
30  
Claimant - Damage - Damaged vehicle - object instance name
No
-
-
Option.
 
DOD+001+:::x--x 
40  
Claimant - Damage - Damaged vehicle - Marque / Modèle / Type
No
-
-
Option.
 
DOD+001 - NME+005+x--x:x--x:x--x 
50  
Claimant - Damage - Damaged vehicle - Numéro plaque d'immatriculation
No
-
-
Option.
 
DOD+001 - RFF+010:x--x:001 
60  
Claimant - Damage - Damaged vehicle - Véhicule immobilisé
Yes
1
Option.
 
DOD+001 - ATT+CP12+x--x 
61 n 
Véhicule - Type de transmission
Yes
2
Option.
 
ROD+001 - ATT+5617+x--x 
62 n 
Claimant - Damage - Damaged vehicle - Véhicule A ou B sur constat européen
Yes
1
Option.
 
DOD+001 - ATT+CP00+x--x 
70  
Claimant - Damage - Damaged vehicle - Driver
No
-
-
Option.
 
DOD+001 - PTY+004 
80  
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - Nom de famille
No
-
-
Cond.
Mandatory 
DOD+001 - PTY+004 - NME+001+x--x 
90  
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - 1er prénom
No
-
-
Cond.
Mandatory 
DOD+001 - PTY+004 - NME+001+:x--x 
100  
Claimant - Damage - Damaged vehicle - Driver - Adresse - rue
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+x--x 
110  
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de maison
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+:x--x 
120  
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de boîte
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+::x--x 
130  
Claimant - Damage - Damaged vehicle - Driver - Adresse - extension
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+::::x--x 
140  
Claimant - Damage - Damaged vehicle - Driver - Adresse - identifiant
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+:::::x--x 
150  
Claimant - Damage - Damaged vehicle - Driver - Adresse - Adresse optimisée suivant fournisseur, code
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+:::::x--x:x--x 
160  
Claimant - Damage - Damaged vehicle - Driver - Adresse - code postal
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002++x--x 
170  
Claimant - Damage - Damaged vehicle - Driver - Adresse - localité
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002+++x--x 
180  
Claimant - Damage - Damaged vehicle - Driver - Adresse - code pays
No
-
-
Option.
 
DOD+001 - PTY+004 - ADR+002++++x--x 
190  
Claimant - Damage - Damaged vehicle - Driver - Date de naissance
No
-
-
Option.
 
DOD+001 - PTY+004 - DTM+001:x--x:001 
200  
Claimant - Damage - Damaged vehicle - Driver - Numéro de téléphone privé
No
-
-
Option.
 
DOD+001 - PTY+004 - COM+001:x--x 
210  
Claimant - Damage - Damaged vehicle - Driver - Numéro de fax
No
-
-
Option.
 
DOD+001 - PTY+004 - COM+002:x--x 
220  
Claimant - Damage - Damaged vehicle - Driver - Adresse boîte postale électronique
No
-
-
Option.
 
DOD+001 - PTY+004 - COM+003:x--x 
230 n 
Claimant - Damage - Damaged vehicle - Driver - Qualité de l'adresse eMail
Yes
1
Cond.
Possibly IF COM+003 NOT Null 
DOD+001 - PTY+004 - ATT+A09F+x--x 

(*) n u d : new / updated / deleted since previous version.

(*bis) u : updated : this can be a codelist-version incrementing.
  Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
  The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
  Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...

(**) 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.