> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M9130 - Description opération de renumérotation de portefeuille / Beschrijving hernummering portefeuille - (Liste des contrats et/ou sinistres impactés / Lijst van de betrokken polissen en/of schadedossiers)-
- 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 : 1
|
| 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 |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
||
| 40 |
Numéro du compte agent identifiant le portefeuille
|
No
|
-
|
-
|
Mand.
|
||
| 50 |
Applicable dès date
|
No
|
-
|
-
|
Cond.
|
if possible for the full list
|
|
| 60 |
Applicable dès échéance mmaaaa
|
No
|
-
|
-
|
Cond.
|
if possible for the full list
|
|
| 70 |
Police
|
No
|
-
|
-
|
Option.
|
0..n occurrences
|
|
| 80 |
Police - Applicable dès date
|
No
|
-
|
-
|
Cond.
|
if needed per individual policy
|
|
| 90 |
Police - Applicable dès échéance mmaaaa
|
No
|
-
|
-
|
Cond.
|
if needed per individual policy
|
|
| 100 |
Police - Ancien numéro de police
|
No
|
-
|
-
|
Mand.
|
||
| 110 |
Police - Nouveau numéro de police
|
No
|
-
|
-
|
Mand.
|
||
| 120 |
Police - Ancien numéro d'avenant
|
No
|
-
|
-
|
Option.
|
||
| 130 |
Police - Nouveau numéro d'avenant
|
No
|
-
|
-
|
Option.
|
||
| 140 |
Dossier sinistre
|
No
|
-
|
-
|
Option.
|
0..n occurrences
|
|
| 150 |
Dossier sinistre - Applicable dès date
|
No
|
-
|
-
|
Cond.
|
if needed per individual claim
|
|
| 160 |
Dossier sinistre - Ancien numéro de dossier
|
No
|
-
|
-
|
Mand.
|
||
| 170 |
Dossier sinistre - Nouveau numéro de dossier
|
No
|
-
|
-
|
Mand.
|
||
| 180 |
Assureur actuel - le "nouveau" dans le cas
|
No
|
-
|
-
|
Mand.
|
||
| 190 |
Assureur actuel - code FSMA
|
No
|
-
|
-
|
Mand.
|
||
| 200 |
Assureur actuel - Ancien numéro du compte producteur
|
No
|
-
|
-
|
Option.
|
||
| 210 |
Assureur précédent - le "ancien" dans le cas
|
No
|
-
|
-
|
Cond.
|
if needed/changed
|
|
| 220 |
Assureur précédent - code FSMA
|
No
|
-
|
-
|
Mand.
|
||
| 230 |
Assureur précédent - Ancien numéro du compte producteur
|
No
|
-
|
-
|
Mand.
|
||
| 240 |
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.