Message Content Inventory |
Identifier : DPTDAMDOD001 - - (Claimant - Damage - Damaged object - données véhicule)
- Approved
, and is part of release 201701 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 2
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
||
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 | n |
Claimant - Damage - Damaged vehicle - Véhicule immobilisé
|
Yes
|
1
|
Option.
|
DOD+001 - ATT+CP12+x--x
|
(*) 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.