> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : EROD060 - Echange contextuel, données famille - (Données famille)
- Approved , and is part of release 201401 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
Version : 1
Status : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2-UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
10  
Contrat
No
-
-
Option.
 
XEH+01+2 
20  
Riskobject, type
No
-
-
Mand.
 
ROD+060 
30  
Adresse optimisée sur base de
Yes
1
Option.
info: a better alternative is to use X099 in segment ADR 
ROD+060 - GIS+A09Y+x--x  
40  
Nom officiel - Nom de famille
No
-
-
Option.
 
ROD+060 - NME+001+x--x 
50  
Adresse - rue
No
-
-
Option.
 
ROD+060 - ADR+002+x--x 
60  
Adresse - numéro de maison
No
-
-
Option.
 
ROD+060 - ADR+002+:x--x 
70  
Adresse - numéro de boîte
No
-
-
Option.
 
ROD+060 - ADR+002+::x--x 
80  
Adresse - extension
No
-
-
Option.
 
ROD+060 - ADR+002+::::x--x 
90  
Adresse - identifiant
No
-
-
Option.
 
ROD+060 - ADR+002+:::::x--x 
100  
Adresse - Adresse optimisée suivant fournisseur, code
No
-
-
Option.
 
ROD+060 - ADR+002+:::::x--x:x--x 
110  
Adresse - code postal
No
-
-
Option.
 
ROD+060 - ADR+002++x--x 
120  
Adresse - localité
No
-
-
Option.
 
ROD+060 - ADR+002+++x--x 
130  
Adresse - code pays
No
-
-
Option.
 
ROD+060 - ADR+002++++x--x 
140  
Type de couverture R.C. - Vie Privée
Yes
2
Option.
 
ROD+060 - ATT+4100+x--x:x--x:x--x:x--x 
150  
Type de famille
Yes
1
Option.
 
ROD+060 - ATT+4160+x--x:x--x:x--x:x--x 
160  
Nombre de personnes dans la famille
No
-
-
Option.
 
ROD+060 - QTY+133:x--x 
170  
Nombre d'enfants
No
-
-
Option.
 
ROD+060 - QTY+050:x--x 
180  
Sous-objet de risque
No
-
-
Option.
0..n presencies 
ROD+060 - SRO+xxx (segment group, multiple occurrencies) 

(*) 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.