> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : ICD5xx - - (Données spécifiques des garanties Auto)
- Approved , and is part of release 201101 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
( Additional information is present below the details-table )
Version : 3
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
5  
Garantie, type
No
-
-
Mand.
 
ICD+5xx 
10  
Degré bonus/malus d'application
Yes
2
Option.
 
ATT+5300 
20  
Degré bonus/malus de référence
Yes
2
Option.
 
ATT+5340 
30  
Degré bonus/malus précédent
Yes
2
Option.
 
ATT+5310 
40  
Classe de bonus/malus d'application
Yes
1
Option.
 
ATT+5301 
50  
Classe de bonus/malus précédente
Yes
1
Option.
 
ATT+5302 
60  
Classe de bonus/malus de référence
Yes
1
Option.
 
ATT+5303 
70 u 
Type de valeur couverte (véhicule)
Yes
5
Option.
 
ATT+5400 
80 d 
Type de franchise
Yes
1
Option.
 
ATT+P11T 
90 d 
Franchise
No
-
-
Option.
 
MOA+033 
100  
Coûts techniques
No
-
-
Mand.
 
MOA+167 
110  
Frais de commercialisation
No
-
-
Mand.
 
MOA+163 
120 d 
Pourcentage franchise ( sur valeur assurée )
No
-
-
Option.
 
PCD+014 
130  
Pourcentage réduction pour pluralité
No
-
-
Option.
 
PCD+017 
140  
Sous-garanties
No
-
-
Option.
 
ISD+xxx 

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

20140314 : this ICD5xx version 3 will not be followed by a ICD5xx version 4, but by the IxD5xx version 4. The reason is we start to implement ISD - Subguarantee. Guarantee and Subguarantee have the same content, except for the fact that the Subguarantee level cannot contain a next (deeper) subguarantee level.