> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Identifier : M0421 - Demande, attestation de sinistres / Vraag, schadeattest - (As in Community MIG's - Echanges Intercompagnies / Inter-maatschappijberichten - Demande attestation de sinistres / Aanvraag schadeattest)- - 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  
Message issuing date and time
No
-
-
Mand.
 
20  
Message content inventory identifier
No
-
-
Mand.
 
30  
Message content inventory version
No
-
-
Mand.
 
40  
Compagnie émettrice
No
-
-
Mand.
 
50  
Compagnie émettrice Assureur - Numéro FSMA
No
-
-
Mand.
 
60  
Compagnie émettrice Assureur - Numéro d'entreprise
No
-
-
Option.
 
70  
Compagnie émettrice Assureur - Numéro d'unité d'établissement
No
-
-
Option.
 
80  
Compagnie émettrice Assureur - LEI
No
-
-
Option.
 
90  
Compagnie émettrice Assureur - Numéro du dossier
No
-
-
Mand.
 
100  
Compagnie destinataire
No
-
-
Mand.
 
110  
Compagnie destinataire Assureur - Numéro FSMA
No
-
-
Mand.
 
120  
Compagnie destinataire Assureur - Numéro d'entreprise
No
-
-
Option.
 
130  
Compagnie destinataire Assureur - Numéro d'unité d'établissement
No
-
-
Option.
 
140  
Compagnie destinataire Assureur - LEI
No
-
-
Option.
 
150  
Compagnie destinataire Assureur - Numéro de police
No
-
-
Mand.
 
160  
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.