> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : IxD3xx - - (Données spécifiques (sous-)garanties Incendie)
- Approved , and is part of release 201501 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
Version : 4
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  
Garantie, type
No
-
-
Mand.
Note this MCI is the one following MCI ICD3xx version 3 
ICD+3xx or ISD+3xx 
20  
Durée indemnisation
No
-
-
Option.
 
DTM+031 
30  
Type de couverture vol contenu
Yes
3
Option.
 
ATT+3464 
40  
Type allocation (domage commercial)
Yes
2
Option.
 
ATT+34B6 
50  
Implication de l'abandon de recours
Yes
1
Option.
 
ATT+M03K 
60  
Application franchise générale contractuelle
No
-
-
Option.
 
BIN+3V40 
70  
Abandon de recours
No
-
-
Option.
 
BIN+3414 
80  
Montant au 1er risque
No
-
-
Option.
 
MOA+035 
90  
Capital - Indemnité journalière
No
-
-
Option.
 
MOA+036 
100  
Nombre de fois appliquer franchise légale
No
-
-
Option.
 
QTY+037 
110  
Pourcentage valeur assurée
No
-
-
Option.
 
PCD+011 
120  
Pourcentage intervention
No
-
-
Option.
 
PCD+012 

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