> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : IxD5xx - - (Données spécifiques (sous-)garanties Auto)
- Approved , and is part of release 201501 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
( Additional information is present below the details-table )
Version : 4
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  
Garantie, type
No
-
-
Mand.
Note this MCI is the one following MCI ICD5xx version 3 
ICD+5xx or ISD+5xx 
20  
Degré bonus/malus d'application
Yes
2
Option.
 
ATT+5300 
30  
Degré bonus/malus de référence
Yes
2
Option.
 
ATT+5340 
40  
Degré bonus/malus précédent
Yes
2
Option.
 
ATT+5310 
50  
Classe de bonus/malus d'application
Yes
1
Option.
 
ATT+5301 
60  
Classe de bonus/malus précédente
Yes
1
Option.
 
ATT+5302 
70  
Classe de bonus/malus de référence
Yes
1
Option.
 
ATT+5303 
80  
Type de valeur couverte (véhicule)
Yes
5
Option.
 
ATT+5400 
90 d 
Coûts techniques
No
-
-
Mand.
 
MOA+167 
100 d 
Frais de commercialisation
No
-
-
Mand.
 
MOA+163 
110  
Pourcentage réduction pour pluralité
No
-
-
Option.
 
PCD+017 

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



Added information :

12/07/2013 :
Généralisation de la possibilité de renseigner au niveau de l'avis et au niveau des garanties la "prime technique ou prime pure", les "coûts techniques", et les "frais de commercialisation".
/ Veralgemening over alle mogelijke takken heen, van deze mogelijkheid om op het niveau van het vervaldagbericht, en op het niveau van de onderliggende waarborgen deze bedragen te vermelden (technische premie of zuivere premie / technische kosten / commercialiseringskosten).