> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Archived, and was part of release 200601 :
 Identifier : M0104ANN - Contrat, avenant - (Avenant d'annulation) - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 1
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
15  
Nature du document
Yes
2
Mand.
 
GIS+EW05 
20  
Date d'annulation
No
-
-
Mand.
 
DTM+002 
25  
Numéro de police
No
-
-
Mand.
 
RFF+001 
30  
Numéro d'avenant
No
-
-
Mand.
 
RFF+002 
35  
Motif d'annulation
Yes
4
Option.
 
ATT+EW01 
40  
Origine de la résiliation
Yes
1
Option.
 
ATT+A314 
45  
Etat de l'acceptation de la nouvelle affaire ou du projet
Yes
2
Option.
 
ATT+A055 
54  
Assureur
No
-
-
Option.
 
PTY+006 
55  
Assureur - Numéro CBFA
No
-
-
Mand.
 
X044 
69  
Intermédiaire
No
-
-
Option.
 
PTY+002 
70  
Intermédiaire - Numéro CBFA
No
-
-
Option.
 
X044(1) 
71  
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
No
-
-
Mand.
 
X044(2) 
75  
Intermédiaire - Référence police producteur
No
-
-
Option.
 
RFF+003 

(*) n u d : new / updated / deleted since previous version.

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