SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0105 - Contrat, modification administrative - (Message générique)
- Approved
, and is part of release 201901 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Broker
Receiver : Insurer
Status : 2 - Version : 4
|
| 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+0105+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory)
|
||
| 11 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0105+++domain++++yyyymmddhhmm+xx:::M0105' (=X943)
|
||
| 12 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0105+++domain++++yyyymmddhhmm+xx:::M0105:4' (=X944)
|
|
| 20 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001:x--x
|
||
| 30 |
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 (NEW)
|
|
| 40 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134 (NEW)
|
|
| 50 |
Encaissement de la police - le terme
|
Yes
|
1
|
Option.
|
ATT+A600+x--x
|
|||
| 60 |
Encaissement de la police - le comptant
|
Yes
|
1
|
Option.
|
ATT+A602+x--x
|
|||
| 70 |
Encaissement de la police - le terme - les échéances intermédiaires
|
Yes
|
1
|
Option.
|
ATT+A603+x--x
|
|||
| 80 |
Mode d'encaissement vis-à-vis client
|
Yes
|
3
|
Option.
|
ATT+A60B+x--x
|
|||
| 81 | n |
Assureur
|
No
|
-
|
-
|
Option.
|
PTY+006
|
|
| 82 | n |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x:006 (X044-1)
|
|
| 83 | n |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+075:x--x
|
|
| 84 | n |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+076:x--x
|
|
| 85 | n |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+107:x--x
|
|
| 90 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
||
| 100 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PTY+002+x--x (X044-1)
|
|
| 110 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x (X044-2)
|
||
| 111 | n |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+075:x--x
|
| 112 | n |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+076:x--x
|
| 113 | n |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+107:x--x
|
|
| 120 | u |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+003:x--x
|
|
| 130 |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PTY+003
|
||
| 140 |
Référence police preneur
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+080:x--x
|
||
| 150 |
Preneur d'assurance - Numéro du compte financier
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+020:x--x
|
||
| 160 |
Preneur d'assurance - Code BIC
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+082:x--x
|
||
| 170 |
Preneur d'assurance - Numéro IBAN
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+077:x--x
|
||
| 171 | n |
Co-preneur d'assurance
|
No
|
-
|
-
|
Option.
|
PTY+017
|
|
| 172 | n |
Co-preneur d'assurance - Référence
|
No
|
-
|
-
|
Option.
|
PTY+017 - RFF+080:x--x
|
|
| 173 | n |
Co-preneur d'assurance - Numéro du compte financier
|
No
|
-
|
-
|
Option.
|
PTY+017 - RFF+020:x--x
|
|
| 174 | n |
Co-preneur d'assurance - Code BIC
|
No
|
-
|
-
|
Option.
|
PTY+017 - RFF+082:x--x
|
|
| 175 | n |
Co-preneur d'assurance - Numéro IBAN
|
No
|
-
|
-
|
Option.
|
PTY+017 - RFF+077:x--x
|
|
| 180 | u |
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.