> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0104ANN - Contrat, avenant - (Avenant d'annulation)-
- Approved
, and is part of release 202401
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) ( Additional information is present below the details-table ) |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 7
|
| 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 |
Contrat informatif - convention gestion flotte
|
Yes
|
1
|
Option.
|
absent defaults to - no -
|
||
| 60 | u |
Nature du document
|
Yes
|
7
|
Mand.
|
Mandatory and with value 6
|
|
| 70 |
Date d'annulation
|
No
|
-
|
-
|
Mand.
|
||
| 80 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
||
| 90 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
||
| 100 |
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.
|
|
| 110 |
MOTIF d'annulation
|
Yes
|
4
|
Mand.
|
|||
| 120 |
Origine de la résiliation
|
Yes
|
2
|
Option.
|
|||
| 130 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
|||
| 140 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
|
| 150 |
Motif rédaction avenant
|
No
|
-
|
-
|
Option.
|
||
| 151 | n |
Quittance annulée
|
No
|
-
|
-
|
Option.
|
Multiple occurences possible
|
| 152 | n |
Quittance annulée - A retourner ou non
|
Yes
|
1
|
Mand.
|
||
| 153 | n |
Quittance annulée - Référence identifiant la quittance
|
No
|
-
|
-
|
Mand.
|
|
| 160 |
Assureur
|
No
|
-
|
-
|
Mand.
|
||
| 170 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
||
| 180 |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
||
| 190 |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
||
| 200 |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
||
| 210 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
||
| 220 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
|
| 230 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
||
| 240 |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
|
| 250 |
Intermédiaire - Numéro unité d'exploitation
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
|
| 260 |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
||
| 270 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
||
| 280 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
||
| 290 |
Intermédiaire - Correspondant - Identifiant plate-forme
|
No
|
-
|
-
|
Option.
|
Actually = XGH+1++:x--x' = recipient user address
|
|
| 300 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
||
| 310 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
||
| 320 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
| 330 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
||
| 340 |
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.