> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 200701 :
Identifier : ICDGEN - - (Données communes garanties)-
- ( UN/Edifact : added info )
- (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info )
Sender :
Receiver :
Status : 3 - Version : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
Indicator
Identifier
Version
10 u 
Garantie, type
No
-
-
Mand.
Generic- possbly completed with one of (ICD1xx.v2 / ICD3xx.v2 / ICD5xx.v2 / ICD6xx.v2) 
15  
Formule - identifiant
No
-
-
Option.
 
20  
Formule - numéro CBFA
No
-
-
Option.
 
25  
Formule - nom
No
-
-
Option.
 
30  
Date d'effet
No
-
-
Option.
 
35  
Date d'expiration
No
-
-
Option.
 
40  
Date première commission
No
-
-
Option.
 
45  
Date dernière commission
No
-
-
Option.
 
50  
Réponse action commerciale
No
-
-
Option.
 
55 u 
Capital
No
-
-
Option.
 
60  
Coûts techniques
No
-
-
Option.
 
65  
Frais de commercialisation
No
-
-
Option.
 
70  
Montant Commission
No
-
-
Option.
 
75  
Montant Charges
No
-
-
Option.
 
80  
Montant Frais
No
-
-
Option.
 
85  
Montant Charges et frais
No
-
-
Option.
 
90 u 
Prime nette
No
-
-
Mand.
 
95  
Frais de fractionnement
No
-
-
Option.
 
100  
Autres coûts à ajouter à la prime nette
No
-
-
Option.
 
105  
Taux de prime
No
-
-
Option.
 
110  
Taux de commission
No
-
-
Option.
 
115  
Pourcentage des charges
No
-
-
Option.
 
120  
Pourcentage des frais
No
-
-
Option.
 
125  
Pourcentage frais et charges
No
-
-
Option.
 
130  
Pourcentage réduction commerciale
No
-
-
Option.
 

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