> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : ECNTRCT - Echange contextuel, données contrat - (Données contrat, pour avenant ou pour consultation) - Approved , and is part of release 201801
- ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender : Any
Receiver : Any
Status : 2 - Version : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10  
Contrat
No
-
-
Mand.
 
XEH+01+2 
20 u 
Numéro de police
No
-
-
Cond.
At least the one or the other 
RFF+001+x--x 
30 n 
Numéro de tarification à la compagnie
No
-
-
Cond.
At least the one or the other 
RFF+004+x--x 
40 u 
Intermédiaire
No
-
-
Mand.
 
PTY+002 
50 u 
Intermédiaire - Numéro FSMA
No
-
-
Option.
 
PTY+002+x--x:006 
60 u 
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
No
-
-
Mand.
 
PTY+002++x--x:002 
70  
Contrat - indication fin dossier
No
-
-
Mand.
 
XET+01 

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