> Syntax independent - MCIs - Messages > Details
|
Message Content Inventory |
Identifier : DPTDAMDOD001 - - (Claimant - Damage - Damaged object - données véhicule)-
- Approved
, and is part of release 202501
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 5
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
10 |
Claimant - Damage - Damaged vehicle
|
No
|
-
|
-
|
Mand.
|
||
20 |
Claimant - Damage - Damaged vehicle - object instance identifier
|
No
|
-
|
-
|
Option.
|
||
30 |
Claimant - Damage - Damaged vehicle - object instance name
|
No
|
-
|
-
|
Option.
|
||
40 |
Claimant - Damage - Damaged vehicle - Marque / Modèle / Type
|
No
|
-
|
-
|
Option.
|
||
50 |
Claimant - Damage - Damaged vehicle - Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Option.
|
||
60 |
Claimant - Damage - Damaged vehicle - Véhicule immobilisé
|
Yes
|
1
|
Option.
|
|||
70 |
Véhicule - Type de transmission
|
Yes
|
2
|
Option.
|
|||
80 |
Claimant - Damage - Damaged vehicle - Véhicule A ou B sur constat européen
|
Yes
|
1
|
Option.
|
|||
90 |
Claimant - Damage - Damaged vehicle - Driver
|
No
|
-
|
-
|
Option.
|
||
100 |
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - Nom de famille
|
No
|
-
|
-
|
Cond.
|
Mandatory
|
|
110 |
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - 1er prénom
|
No
|
-
|
-
|
Cond.
|
Mandatory
|
|
120 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - rue
|
No
|
-
|
-
|
Option.
|
||
130 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
||
140 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
||
150 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - extension
|
No
|
-
|
-
|
Option.
|
||
160 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
||
170 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
||
180 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - code postal
|
No
|
-
|
-
|
Option.
|
||
190 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - localité
|
No
|
-
|
-
|
Option.
|
||
200 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - code pays
|
No
|
-
|
-
|
Option.
|
||
210 |
Claimant - Damage - Damaged vehicle - Driver - Date de naissance
|
No
|
-
|
-
|
Option.
|
||
220 |
Claimant - Damage - Damaged vehicle - Driver - Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
||
230 |
Claimant - Damage - Damaged vehicle - Driver - Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
240 |
Claimant - Damage - Damaged vehicle - Driver - Adresse boîte postale électronique
|
No
|
-
|
-
|
Option.
|
||
250 | d |
Claimant - Damage - Damaged vehicle - Driver - Qualité de l'adresse eMail
|
Yes
|
1
|
Cond.
|
Possibly IF COM+003 NOT Null
|
(*) 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.