SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EROD003 - Echange contextuel, données engin nautique - (Données engin nautique)
- Approved
, and is part of release 202101 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 2 - Version : 3
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Contrat
|
No
|
-
|
-
|
Mand.
|
XEH+01+2
|
||
| 20 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ROD+003
|
||
| 30 |
Bateau, nom
|
No
|
-
|
-
|
Mand.
|
ROD+003 - NME+001+x--x
|
||
| 40 |
Bateau, marque
|
No
|
-
|
-
|
Option.
|
ROD+003 - NME+005+x--x
|
||
| 50 |
Bateau, marque et modèle
|
No
|
-
|
-
|
Option.
|
ROD+003 - NME+005+x--x:x--x
|
||
| 60 |
Bateau, pays de construction (code et nom)
|
No
|
-
|
-
|
Option.
|
ROD+003 - ADR+018++++x--x+x--x
|
||
| 70 |
Bateau, année de construction
|
No
|
-
|
-
|
Option.
|
ROD+003 - DTM+012:x--x:004
|
||
| 80 |
Bateau, numéro d'identification de la coque
|
No
|
-
|
-
|
Option.
|
ROD+003 - RFF+091:x--x
|
||
| 90 |
Bateau, lettre de pavillon - code
|
No
|
-
|
-
|
Option.
|
ROD+003 - RFF+092:x--x
|
||
| 100 |
Bateau, lettre de pavillon - numéro
|
No
|
-
|
-
|
Option.
|
ROD+003 - RFF+093:x--x
|
||
| 110 |
Bateau, plaque d'immatriculation numéro
|
No
|
-
|
-
|
Option.
|
ROD+003 - RFF+010:x--x
|
||
| 120 |
Bateau, utilisation
|
Yes
|
1
|
Mand.
|
ROD+003 - ATT+5800+x--x
|
|||
| 130 |
Bateau, type
|
Yes
|
1
|
Option.
|
ROD+003 - ATT+5801+x--x
|
|||
| 140 |
Bateau, gréement
|
Yes
|
1
|
Option.
|
ROD+003 - ATT+5802+x--x
|
|||
| 150 |
Bateau, matériaux de construction principal
|
Yes
|
1
|
Option.
|
ROD+003 - ATT+5803+x--x
|
|||
| 151 | n |
Bateau, a cabine
|
No
|
-
|
-
|
Option.
|
ROD+003 - BIN+5806+x--x
|
|
| 160 |
Bateau, longueur hors tout en mètres
|
No
|
-
|
-
|
Option.
|
ROD+003 - QTY+145:x--x:2:008
|
||
| 170 |
Bateau, longueur de la coque en mètres
|
No
|
-
|
-
|
Option.
|
ROD+003 - QTY+024:x--x:2:008
|
||
| 180 |
Bateau, largeur de la coque en mètres
|
No
|
-
|
-
|
Option.
|
ROD+003 - QTY+026:x--x:2:008
|
||
| 190 |
Bateau, tirant d'eau en mètres
|
No
|
-
|
-
|
Option.
|
ROD+003 - QTY+146:x--x:2:008
|
||
| 200 |
Bateau - Certificat de navigation, nom
|
No
|
-
|
-
|
Option.
|
Multiple documents are a possibility
|
ROD+003 - DOC+056+:::x--x
|
|
| 210 |
Bateau - Certificat de navigation, date de début de validité
|
No
|
-
|
-
|
Option.
|
ROD+003 - DOC+056 - DTM+032:jjmmaaaa:001
|
||
| 220 |
Bateau - Certificat de navigation, date de fin de validité
|
No
|
-
|
-
|
Option.
|
ROD+003 - DOC+056 - DTM+038:jjmmaaaa:001
|
||
| 230 |
Bateau - Certificat de navigation, mediafile
|
No
|
-
|
-
|
Option.
|
ROD+003 - DOC+056 - MMD+x--x+...
|
||
| 240 |
Bateau - Port d'attache, nom
|
No
|
-
|
-
|
Option.
|
ROD+003 - PTY+055 - NME+001+x--x
|
||
| 250 |
Bateau - Chantier de construction, nom
|
No
|
-
|
-
|
Option.
|
ROD+003 - PTY+056 - NME+001+x--x
|
||
| 260 |
Garantie
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
ROD+003 - ICD+xxx
|
|
| 270 |
Bateau - Moteur, marque
|
No
|
-
|
-
|
Option.
|
0..n presencies - Multiple engines are a possibility
|
ROD+003 - SRO+013 - NME+005+x--x
|
|
| 280 |
Bateau - Moteur, marque et type
|
No
|
-
|
-
|
Option.
|
ROD+003 - SRO+013 - NME+005+x--x:x--x
|
||
| 290 |
Bateau - Moteur, année de construction
|
No
|
-
|
-
|
Option.
|
ROD+003 - SRO+013 - DTM+012:x--x:004
|
||
| 300 |
Bateau - Moteur, numéro de série
|
No
|
-
|
-
|
Option.
|
ROD+003 - SRO+013 - RFF+094:x--x
|
||
| 310 |
Bateau - Moteur, installation
|
Yes
|
1
|
Option.
|
ROD+003 - SRO+013 - ATT+5804+x--x
|
|||
| 320 |
Bateau - Moteur, carburant
|
Yes
|
1
|
Option.
|
ROD+003 - SRO+013 - ATT+5805+x--x
|
|||
| 330 |
Bateau - Moteur, description
|
No
|
-
|
-
|
Option.
|
ROD+003 - SRO+013 - FTX+019+x--x
|
||
(*) n u d : new / updated / deleted since previous version.
(**) 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.