> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DEDxxx - - (Données franchise)-
- Approved
, and is part of release 202101
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) ( Additional information is present below the details-table ) |
Sender :
Receiver :
Status : 2 - Version : 3
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
| 10 |
Franchise - type
|
No
|
-
|
-
|
Option.
|
See the Recommendations page.
|
|
| 20 |
Expression en (taux, montant, durée)
|
Yes
|
2
|
Option.
|
|||
| 30 | u |
Base de calcul
|
Yes
|
4
|
Option.
|
||
| 40 |
Type en terminologie Informex
|
Yes
|
1
|
Option.
|
|||
| 50 |
Rachat du délai de carence
|
No
|
-
|
-
|
Option.
|
||
| 60 |
Maintien du délai de carence après 60 ans
|
No
|
-
|
-
|
Option.
|
||
| 70 |
Rachat de la franchise
|
No
|
-
|
-
|
Option.
|
||
| 80 |
Franchise contractuelle
|
No
|
-
|
-
|
Option.
|
||
| 90 |
La franchise n'est pas d'application
|
No
|
-
|
-
|
Option.
|
||
| 100 |
Franchise seuil
|
No
|
-
|
-
|
Option.
|
||
| 110 |
Franchise jeune conducteur
|
No
|
-
|
-
|
Option.
|
||
| 120 |
Franchise territoriale
|
No
|
-
|
-
|
Option.
|
||
| 130 |
Franchise consignée
|
No
|
-
|
-
|
Option.
|
||
| 140 |
Franchise en dommages corporels
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
|
| 150 |
Franchise en dommages matériels
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
|
| 160 |
Franchise en dommages mixtes
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
|
| 170 |
Franchise en dommages immatériels
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
|
| 180 |
Franchise en objets confiés
|
No
|
-
|
-
|
Cond.
|
Possibly when under ICD4xx guarantee
|
|
| 190 | u |
Franchise, montant
|
No
|
-
|
-
|
Option.
|
Index information if relevant
|
| 200 | u |
Valeur minimale
|
No
|
-
|
-
|
Option.
|
Index information if relevant
|
| 210 | u |
Valeur maximale
|
No
|
-
|
-
|
Option.
|
Index information if relevant
|
| 220 | n |
Franchise - intervention dès incapacité pourcentage
|
No
|
-
|
-
|
Option.
|
|
| 221 | n |
Franchise - pourcentage sur valeur assurée
|
No
|
-
|
-
|
Option.
|
|
| 222 | n |
Franchise - pourcentage sur montant des dégats
|
No
|
-
|
-
|
Option.
|
|
| 223 | u |
Franchise - pourcentage (sur montant spécifié)
|
No
|
-
|
-
|
Option.
|
see P11U value
|
| 224 | n |
Franchise - pourcentage minimal en incapacité de travail
|
No
|
-
|
-
|
Option.
|
|
| 230 |
Franchise, date de début de période
|
No
|
-
|
-
|
Option.
|
||
| 240 |
Franchise, date de fin de période
|
No
|
-
|
-
|
Option.
|
||
| 250 |
Délai de carence en jours, semaines, mois, ...
|
No
|
-
|
-
|
Option.
|
||
| 260 |
Délai d'attente en jours, semaines, mois, ...
|
No
|
-
|
-
|
Option.
|
||
| 270 |
Franchise, Durée en années, mois, semaines ou jours
|
No
|
-
|
-
|
Option.
|
||
| 280 |
Franchise territoriale, le pays, code et/ou nom
|
No
|
-
|
-
|
Option.
|
||
(*) 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.