> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : DPTDAMDODGEN - - (Claimant - Damage - Damaged object - données communes)
- Approved , and is part of release 201701 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
( Additional information is present below the details-table )
Version : 2
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 u 
Claimant - Damage - Damaged object - Type of object
No
-
-
Mand.
Extendible with one of : (DPTDAMDOD001v2 / DPTDAMDOD010v1 / DPTDAMDOD030v1) 
DOD+xxx 
20  
Claimant - Damage - Damaged object - object instance identifier
No
-
-
Option.
 
DOD+xxx+x--x:002/003 
30  
Claimant - Damage - Damaged object - object instance name
No
-
-
Option.
 
DOD+xxx+:::x--x 
40  
Claimant - Damage - Damaged object - L'objet des dommages est décrit
Yes
1
Option.
 
DOD+xxx - ATT+9910+x--x 
50  
Claimant - Damage - Damaged object - Application de la règle proportionelle
No
-
-
Option.
 
DOD+xxx - BIN+C066:x--x 
60  
Claimant - Damage - Damaged object - Montant estimation des dommages
No
-
-
Option.
 
DOD+xxx - MOA+181:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
70  
Claimant - Damage - Damaged object - Montant des dommages payés
No
-
-
Option.
 
DOD+xxx - MOA+182:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
80  
Claimant - Damage - Damaged object - Montant des dommages réservés
No
-
-
Option.
 
DOD+xxx - MOA+183:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
90  
Claimant - Damage - Damaged object - Montant des dommages recouvrables
No
-
-
Option.
 
DOD+xxx - MOA+184:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
100  
Claimant - Damage - Damaged object - Montant des dommages en franchise
No
-
-
Option.
 
DOD+xxx - MOA+185:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
110  
Claimant - Damage - Damaged object - Pourcentage de récupération appliqué sur le taux de TVA (sininstres)
No
-
-
Option.
 
DOD+xxx - PCD+060:9--9:2 
120  
Claimant - Damage - Damaged object - Valuation
No
-
-
Option.
Multiple presencies possible 
DOD+xxx - VAL+xxx 
130  
Claimant - Damage - Damaged object - Valuation - Date d'envoi de la mission d'expertise
No
-
-
Option.
 
DOD+xxx - VAL+xxx - DTM+051:ddmmyyyy:001 
140  
Claimant - Damage - Damaged object - Valuation - Date réception rapport d'expertise
No
-
-
Option.
 
DOD+xxx - VAL+xxx - DTM+052:ddmmyyyy:001 
150  
Claimant - Damage - Damaged object - Valuation - Durée chômage en jours
No
-
-
Option.
 
DOD+xxx - VAL+xxx - DTM+054:9--9:111 
160  
Claimant - Damage - Damaged object - Valuation - Origine de la demande d'expertise
Yes
1
Option.
 
DOD+xxx - VAL+xxx - ATT+C418+x--x 
170  
Claimant - Damage - Damaged object - Valuation - Type de mandat de l'expert
Yes
2
Option.
Multiple presencies possible 
DOD+xxx - VAL+xxx - ATT+C42F+x--x 
180  
Claimant - Damage - Damaged object - Valuation - Type de mission
Yes
2
Option.
 
DOD+xxx - VAL+xxx - ATT+C41Z+x--x 
190  
Claimant - Damage - Damaged object - Valuation - Application de la convention RDR
No
-
-
Option.
 
DOD+xxx - VAL+xxx - BIN+C060:x--x 
200  
Claimant - Damage - Damaged object - Valuation - Perte totale
No
-
-
Option.
 
DOD+xxx - VAL+xxx - BIN+C452:x--x 
210  
Claimant - Damage - Damaged object - Valuation - Montant d'expertise (1)
No
-
-
Option.
 
DOD+xxx - VAL+xxx - MOA+071:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
220  
Claimant - Damage - Damaged object - Valuation - Coûts de dépannage
No
-
-
Option.
 
DOD+xxx - VAL+xxx - MOA+075:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
230  
Claimant - Damage - Damaged object - Valuation - Coûts de chômage
No
-
-
Option.
 
DOD+xxx - VAL+xxx - MOA+076:9--9:EUR:2:001+x--x:9--9:2+9--9:2 
240  
Claimant - Damage - Damaged object - Valuation - Coûts de gardiennage
No
-
-
Option.
 
DOD+xxx - VAL+xxx - MOA+077:9--9:EUR:2:001+x--x:9--9:2+9--9:2 

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



Added information :

Structuring a coherent set of claims messages.
This sub-structure is used in the M02xx messages.