Syntax Independent Components
Implementation Related Components
Implementation Related Components
|
|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : ROD110 - - (Données voyage / Gegevens reis) - Approved , and is part of release 202001 - ( UN/Edifact MIG : Fr / Nl ) |
Version : 1 Status : 2 |
| n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
XML-tag |
UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
InsuranceObject Travel
|
ROD+110
|
||
Date de début de période - départ
|
No
|
-
|
-
|
Option.
|
PremiumPeriod PeriodStartDate
|
DTM+041
|
||
Date de fin de période - retour
|
No
|
-
|
-
|
Option.
|
Travel ReturnDate
|
DTM+022
|
||
Description - Destination
|
No
|
-
|
-
|
Option.
|
FTX+019
|
|||
Nombre de voyageurs
|
No
|
-
|
-
|
Option.
|
Travel TravellersCount
|
QTY+043
|
||
Type de transport
|
Yes
|
8040
|
1
|
Option.
|
Travel TravelTypeCode
|
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.