Syntax Independent Components
Implementation Related Components
Implementation Related Components
|
|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : ICD6xx - - (Données spécifiques des garanties A.T.) - Approved , and is part of release 200701 - ( UN/Edifact MIG : Fr / Nl ) |
Version : 2 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 |
||||||
Garantie, type
|
No
|
-
|
-
|
Mand.
|
Guarantee
|
ICD+6xx
|
||
Prime adaptable à l'évolution du risque
|
No
|
-
|
-
|
Option.
|
Guarantee PremiumAdaptableToRiskEvolutionIndicator
|
BIN+641B
|
||
u |
Prime unitaire
|
No
|
-
|
-
|
Option.
|
Guarantee PerUnitPremiumAmount
|
MOA+175
|
|
Taux de prime
|
No
|
-
|
-
|
Option.
|
Premium PremiumRate
|
PCD+016
|
||
Sous-garanties
|
No
|
-
|
-
|
Option.
|
Guarantee withSubGuarantee isGuarantee
|
ISD+xxx
|
||
(*) 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.