Message Content Inventory |
Identifier : M0104SUS - Contrat, avenant - (Avenant de suspension)
- Approved
, and is part of release 202401 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 6
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
||
Indicator |
Identifier |
Version |
||||||
10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0104+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory)
|
||
20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0104+++domain++++yyyymmddhhmm+xx:::M0104SUS' (=X943)
|
||
30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0104+++domain++++yyyymmddhhmm+xx:::M0104SUS:6' (=X944)
|
|
40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
XEH+01+2
|
||
50 | u |
Nature du document
|
Yes
|
7
|
Mand.
|
Mandatory and with value 7
|
GIS+EW05+7
|
|
60 |
Date de suspension
|
No
|
-
|
-
|
Mand.
|
DTM+060
|
||
70 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001
|
||
80 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
RFF+002
|
||
90 |
GUID (Globally Unique IDentifier) du message, sera référencé par le(s) document(s) annexe(s)
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
RFF+084
|
|
100 |
MOTIF de suspension
|
Yes
|
3
|
Option.
|
ATT+A311+x--x
|
|||
110 |
Origine de la résiliation
|
Yes
|
2
|
Option.
|
ATT+A314+x--x
|
|||
120 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
ATT+A055+x--x
|
|||
130 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134
|
|
131 | n |
Quittance annulée
|
No
|
-
|
-
|
Option.
|
Multiple occurences possible
|
ACT+007
|
132 | n |
Quittance annulée - A retourner ou non
|
Yes
|
1
|
Mand.
|
ACT+007 - GIS+B057
|
||
133 | n |
Quittance annulée - Référence identifiant la quittance
|
No
|
-
|
-
|
Mand.
|
ACT+007 - RFF+123
|
|
140 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PTY+006
|
||
150 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x:006
|
||
151 |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+075:x--x
|
||
152 |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+076:x--x
|
||
153 |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+107:x--x
|
||
160 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
||
170 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PTY+002+x--x:006
|
|
180 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x:002
|
||
181 |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+075:x--x
|
|
182 |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+076:x--x
|
|
183 |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+107:x--x
|
||
190 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+003
|
||
260 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210
|
||
270 |
Intermédiaire - Correspondant - Identifiant plate-forme
|
No
|
-
|
-
|
Option.
|
Actually = XGH+1++:x--x' = recipient user address
|
PTY+002 - RPT+210+x--x:008 (ou 009)
|
|
280 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - NME+001
|
||
290 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - COM+006
|
||
300 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - COM+002
|
||
310 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - COM+003
|
||
320 |
Message end
|
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.