> Syntax independent - MCIs - Messages > Details
|
Message Content Inventory |
Identifier : M0603 - Récapitulation, fichier(s) PRENOT / Samenvatting, PRENOT bestanden - (Totaux de contrôle fichier(s) PRENOT / PRENOT bestanden, controle-totalen)-
- Approved
, and is part of release 201901
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 3
|
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 |
Date de comptabilisation
|
No
|
-
|
-
|
Option.
|
||
50 |
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.
|
|
60 |
Mode d'encaissement de la quittance
|
Yes
|
1
|
Option.
|
|||
70 |
Unité monétaire
|
Yes
|
3
|
Option.
|
|||
80 |
Prime nette
|
No
|
-
|
-
|
Option.
|
||
90 |
Montant commission
|
No
|
-
|
-
|
Option.
|
||
100 |
Montant à payer
|
No
|
-
|
-
|
Option.
|
||
110 |
Nombre de documents expédiés pour ce mode d'encaissement
|
No
|
-
|
-
|
Option.
|
||
120 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
|
130 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
||
140 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
|
150 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
||
160 |
Intermédiaire - Code carte d'échange
|
No
|
-
|
-
|
Mand.
|
||
161 | n |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
162 | n |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
163 | n |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
|
170 |
Assureur
|
No
|
-
|
-
|
Mand.
|
||
180 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
||
190 | u |
Assureur - Code carte d'échange
|
No
|
-
|
-
|
Option.
|
|
191 | n |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
|
192 | n |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
|
193 | n |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
|
200 | u |
Message end
|
No
|
-
|
-
|
Mand.
|
(*) 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.