> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : ICDGEN - - (Données communes garanties)
- ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
Version : 3
Status : 3
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.
Generic- possbly completed with one of (ICD1xx.v2 / ICD3xx.v2 / ICD5xx.v2 / ICD6xx.v2) 
ICD+xxx 
15  
Formule - identifiant
No
-
-
Option.
 
IFD+xxx 
20  
Formule - numéro CBFA
No
-
-
Option.
 
X902 
25  
Formule - nom
No
-
-
Option.
 
X063 
30  
Date d'effet
No
-
-
Option.
 
DTM+008 
35  
Date d'expiration
No
-
-
Option.
 
DTM+138 
40  
Date première commission
No
-
-
Option.
 
DTM+023 
45  
Date dernière commission
No
-
-
Option.
 
DTM+024 
50  
Réponse action commerciale
No
-
-
Option.
 
BIN+A537 
55 n 
Présence d'une franchise
No
-
-
Option.
 
BIN+3419 
60 n 
Rachat de franchise
No
-
-
Option.
 
BIN+3423 
65  
Capital
No
-
-
Option.
 
MOA+004 
70  
Coûts techniques
No
-
-
Option.
 
MOA+167 
75  
Frais de commercialisation
No
-
-
Option.
 
MOA+163 
80  
Montant Commission
No
-
-
Option.
 
MOA+015 
85  
Montant Charges
No
-
-
Option.
 
MOA+016 
90  
Montant Frais
No
-
-
Option.
 
MOA+017 
95  
Montant Charges et frais
No
-
-
Option.
 
MOA+018 
100  
Prime nette
No
-
-
Mand.
 
MOA+005 
105  
Frais de fractionnement
No
-
-
Option.
 
MOA+039 
110  
Autres coûts à ajouter à la prime nette
No
-
-
Option.
 
MOA+105 
115  
Taux de prime
No
-
-
Option.
 
PCD+016 
120  
Taux de commission
No
-
-
Option.
 
PCD+005 
125  
Pourcentage des charges
No
-
-
Option.
 
PCD+006 
130  
Pourcentage des frais
No
-
-
Option.
 
PCD+007 
135  
Pourcentage frais et charges
No
-
-
Option.
 
PCD+010 
140  
Pourcentage réduction commerciale
No
-
-
Option.
 
PCD+036 

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