> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201701 : Identifier : M0126 - Contrat, message production origine assureur hors contrat - (MPB : Message Production, mais hors contrat / Productie Bericht, maar los van bestaand contract)- - ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 5
|
| 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 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
|
| 40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
||
| 50 |
Type de police
|
Yes
|
9
|
Option.
|
|||
| 60 |
Produit
|
No
|
-
|
-
|
Option.
|
if present- then both code AND label
|
|
| 70 |
Date d'effet
|
No
|
-
|
-
|
Mand.
|
||
| 80 |
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.
|
|
| 90 |
Référence des paiements
|
No
|
-
|
-
|
Option.
|
||
| 100 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
|
| 110 |
Acte de gestion
|
No
|
-
|
-
|
Mand.
|
multiple presencies
|
|
| 120 |
Acte de gestion - Destinataire documents demandés
|
Yes
|
1
|
Option.
|
|||
| 130 |
Acte de gestion - Code MPB origine assureur (texte libre)
|
Yes
|
4
|
Cond.
|
Mandatory when text is present
|
||
| 140 |
Acte de gestion - Texte de communication
|
No
|
-
|
-
|
Option.
|
||
| 150 |
Assureur
|
No
|
-
|
-
|
Mand.
|
||
| 160 | u |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
|
| 170 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
|||
| 180 |
Assureur - Correspondant - Correspondant, gestionnaire
|
No
|
-
|
-
|
Option.
|
||
| 190 |
Assureur - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
||
| 200 |
Assureur - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
||
| 210 |
Assureur - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
| 220 |
Assureur - Correspondant - e-Mail
|
No
|
-
|
-
|
Mand.
|
||
| 230 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
||
| 240 | u |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
| 250 | u |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
|
| 260 |
Intermédiaire - Numéro du dossier
|
No
|
-
|
-
|
Option.
|
||
| 261 | n |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
| 262 | n |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
| 270 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
||
| 280 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
||
| 290 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
||
| 300 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
| 310 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
||
| 320 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Option.
|
one of PTY003GRPv9- PTY003PMv9- PTY003PPv10
|
| 330 | u |
Objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies RODGENv12
|
(*) 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.