> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Identifier : M0151 - Contrat, Attestation de sinistre - partie contrat / Contract, Schadeattest - gedeelte contract - (As in Community MIG's - Echanges Intercompagnies - Attestation de sinistres - partie contrat - Voir M0213 pour la partie sinistre(s) / Inter-maatschappijberichten - Schadeattest - gedeelte contract - Zie M0213 voor gedeelte schade(s))- - Approved , and is part of release 200601
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info )
Sender : Insurer
Receiver : Insurer
Status : 2 - Version : 1
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
Indicator
Identifier
Version
10 d 
Message envelope, sender identification, public
No
-
-
Mand.
deleted as incorporated in MCI AMEMEv1 
20 d 
Message envelope, sender identification, private
No
-
-
Option.
deleted as incorporated in MCI AMEMEv1 
30 d 
Message envelope, recipient identification, public
No
-
-
Mand.
deleted as incorporated in MCI AMEMEv1 
40 d 
Message envelope, recipient identification, private
No
-
-
Option.
deleted as incorporated in MCI AMEMEv1 
50 d 
Message envelope, content type est attestation de sinistre
No
-
-
Option.
deleted as incorporated in MCI AMEMEv1 
60  
Contrat, en domaine auto
No
-
-
Mand.
 
70 u 
Message content inventory identifier
No
-
-
Mand.
 
80 u 
Message content inventory version
No
-
-
Mand.
 
90  
Date d'échéance principale
No
-
-
Mand.
 
100  
Numéro de police
No
-
-
Mand.
 
110  
Assureur
No
-
-
Mand.
 
120  
Assureur - Numéro CBFA
No
-
-
Mand.
 
130  
Assureur - Nom officiel (Nom)
No
-
-
Mand.
 
140  
Assureur - Adresse (rue, numéro, boîte, code postal, commune, code pays, pays)
No
-
-
Mand.
 
150  
Preneur d'assurance
No
-
-
Mand.
 
160  
Preneur - Nom officiel (Nom de famille, max. 3 prénoms, titre)
No
-
-
Mand.
 
170  
Preneur - Adresse (rue, numéro, boîte, code postal, commune, code pays, pays)
No
-
-
Mand.
 
180  
Objet de risque, véhicule
No
-
-
Mand.
 
190  
Objet de risque, véhicule - numéro de plaque
No
-
-
Mand.
 
200  
Objet de risque, véhicule - type de véhicule
Yes
1
Mand.
 
210  
Objet de risque, véhicule - SAS usage du véhicule assuré
Yes
1
Mand.
 
220  
Objet de risque, véhicule - Garantie, R.C.
No
-
-
Mand.
 
230  
Objet de risque, véhicule - Garantie, R.C. - Date d'effet
No
-
-
Mand.
 
240  
Objet de risque, véhicule - Garantie, R.C. - Date de fin
No
-
-
Mand.
 
250  
Objet de risque, véhicule - Garantie, R.C. - Degrée bonus/malus d'application
Yes
2
Mand.
 
260  
Message End
No
-
-
Mand.
 

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