> Syntax independent - MCIs - Messages > Details
|
Message Content Inventory |
Identifier : EROD060 - Echange contextuel, données famille - (Données famille)-
- Approved
, and is part of release 201401
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 2 - Version : 1
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
10 |
Contrat
|
No
|
-
|
-
|
Mand.
|
||
20 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
||
30 |
Adresse optimisée sur base de
|
Yes
|
1
|
Option.
|
info: a better alternative is to use X099 in segment ADR
|
||
40 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Option.
|
||
50 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
||
60 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
||
70 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
||
80 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
||
90 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
||
100 |
Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
||
110 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
||
120 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
||
130 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
||
140 |
Type de couverture R.C. - Vie Privée
|
Yes
|
2
|
Option.
|
|||
150 |
Type de famille
|
Yes
|
1
|
Option.
|
|||
160 |
Nombre de personnes dans la famille
|
No
|
-
|
-
|
Option.
|
||
170 |
Nombre d'enfants
|
No
|
-
|
-
|
Option.
|
||
180 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
(*) 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.