SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DPTDAMDODGEN - - (Claimant - Damage - Damaged object - données communes)
- Approved
, and is part of release 202201 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & 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) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 | u |
Claimant - Damage - Damaged object - Type of object
|
No
|
-
|
-
|
Mand.
|
Extendible with one of : (DPTDAMDOD001v4 / DPTDAMDOD01xv1 / DPTDAMDOD030v1)
|
ObjectDamaged...
|
| 20 |
Claimant - Damage - Damaged object - object instance identifier
|
No
|
-
|
-
|
Option.
|
RiskObjectDetail ObjectIdentifier CodeListIdentifier
|
||
| 30 |
Claimant - Damage - Damaged object - object instance name
|
No
|
-
|
-
|
Option.
|
RiskObjectDetail ObjectName
|
||
| 40 |
Claimant - Damage - Damaged object - L'objet des dommages est décrit
|
Yes
|
1
|
Option.
|
TheObjectOfDamagesIsDefinedCode
|
|||
| 50 |
Claimant - Damage - Damaged object - Application de la règle proportionelle
|
No
|
-
|
-
|
Option.
|
ApplicationOfTheProportionalityRuleBinary
|
||
| 60 |
Claimant - Damage - Damaged object - Montant estimation des dommages
|
No
|
-
|
-
|
Option.
|
EstimatedDamagesAmount
|
||
| 70 |
Claimant - Damage - Damaged object - Montant des dommages payés
|
No
|
-
|
-
|
Option.
|
DamagesPaidAmount
|
||
| 80 |
Claimant - Damage - Damaged object - Montant des dommages réservés
|
No
|
-
|
-
|
Option.
|
DamagesReservedAmount
|
||
| 90 |
Claimant - Damage - Damaged object - Montant des dommages recouvrables
|
No
|
-
|
-
|
Option.
|
RecoverableDamagesAmount
|
||
| 100 |
Claimant - Damage - Damaged object - Montant des dommages en franchise
|
No
|
-
|
-
|
Option.
|
DamagesBelowDeductibleAmount
|
||
| 110 |
Claimant - Damage - Damaged object - Pourcentage de récupération appliqué sur le taux de TVA (sininstres)
|
No
|
-
|
-
|
Option.
|
VatExemptionInClaimPercentage
|
||
| 120 |
Claimant - Damage - Damaged object - Valuation
|
No
|
-
|
-
|
Option.
|
Multiple presencies possible
|
Valuation...
|
|
| 130 |
Claimant - Damage - Damaged object - Valuation - Date d'envoi de la mission d'expertise
|
No
|
-
|
-
|
Option.
|
AssessmentRequestExpeditionDate
|
||
| 140 |
Claimant - Damage - Damaged object - Valuation - Date réception rapport d'expertise
|
No
|
-
|
-
|
Option.
|
AssessmentReportReceptionDate
|
||
| 150 |
Claimant - Damage - Damaged object - Valuation - Durée chômage en jours
|
No
|
-
|
-
|
Option.
|
DeprivationOrLossOfUseDuration
|
||
| 160 |
Claimant - Damage - Damaged object - Valuation - Origine de la demande d'expertise
|
Yes
|
1
|
Option.
|
OriginOfTheAssessmentRequestCode
|
|||
| 170 |
Claimant - Damage - Damaged object - Valuation - Type de mandat de l'expert
|
Yes
|
3
|
Option.
|
Multiple presencies possible
|
MissionOfTheAssessorCode
|
||
| 180 |
Claimant - Damage - Damaged object - Valuation - Type de mission
|
Yes
|
2
|
Option.
|
MissionCode
|
|||
| 190 |
Claimant - Damage - Damaged object - Valuation - Application de la convention RDR
|
No
|
-
|
-
|
Option.
|
ApplicationOfTheKnockForKnockConventionBinary
|
||
| 200 |
Claimant - Damage - Damaged object - Valuation - Perte totale
|
No
|
-
|
-
|
Option.
|
TotalLossAssessmentBinary
|
||
| 210 |
Claimant - Damage - Damaged object - Valuation - Montant d'expertise (1)
|
No
|
-
|
-
|
Option.
|
AssessmentValue1Amount
|
||
| 220 |
Claimant - Damage - Damaged object - Valuation - Coûts de dépannage
|
No
|
-
|
-
|
Option.
|
TowingCostsAmount
|
||
| 230 |
Claimant - Damage - Damaged object - Valuation - Coûts de chômage
|
No
|
-
|
-
|
Option.
|
DeprivationOrLossOfUseCostsAmount
|
||
| 240 |
Claimant - Damage - Damaged object - Valuation - Coûts de gardiennage
|
No
|
-
|
-
|
Option.
|
GaragingCostsAmount
|
||
(*) 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.