SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EROD110 - Echange contextuel, données voyage - (Données voyage / Gegevens reis)
- Approved
, and is part of release 202001 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & 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) |
TB2 UN/EDIFACT representation |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ROD+110
|
||
| 15 |
Date de début de période - départ
|
No
|
-
|
-
|
Option.
|
DTM+041
|
||
| 20 |
Date de fin de période - retour
|
No
|
-
|
-
|
Option.
|
DTM+022
|
||
| 25 |
Destination
|
No
|
-
|
-
|
Option.
|
FTX+019
|
||
| 30 |
Nombre de voyageurs
|
No
|
-
|
-
|
Option.
|
QTY+043
|
||
| 35 |
Type de transport
|
Yes
|
1
|
Option.
|
ATT+8040
|
|||
(*) 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.