> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : EROD009 - Echange contextuel, données engin aérien - (Données engin aérien)
- Approved , and is part of release 201801 - ( 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 Engin aérien
No
-
-
Mand.
 
ROD+009 
30  
Engin aérien - Marque et modèle
No
-
-
Mand.
 
ROD+009 - NME+005+x--x:x--x 
40  
Engin aérien - Marques d'identification
No
-
-
Cond.
pour tout engin immatriculé 
ROD+009 - NME+006+x--x 
50  
Engin aérien - Numéro de série de fabrication (n° chassis)
No
-
-
Mand.
 
ROD+009 - RFF+011:x--x:001 
60  
Engin aérien - Type d'engin aérien
Yes
1
Mand.
 
ROD+009 - ATT+5900+x--x 
70  
Engin aérien - Classe d'utilisation du drone
Yes
1
Cond.
IF ATT+5900 = 06 Drone 
ROD+009 - ATT+5910+x--x 
80  
Engin aérien - Masse maximale de décollage en kg
No
-
-
Mand.
 
ROD+009 - QTY+154:x--x:2:003 

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