> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 200701 :
Identifier : ICDGEN - - (Données communes garanties) - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & 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)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10 u 
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 u 
Capital
No
-
-
Option.
 
MOA+004 
60  
Coûts techniques
No
-
-
Option.
 
MOA+167 
65  
Frais de commercialisation
No
-
-
Option.
 
MOA+163 
70  
Montant Commission
No
-
-
Option.
 
MOA+015 
75  
Montant Charges
No
-
-
Option.
 
MOA+016 
80  
Montant Frais
No
-
-
Option.
 
MOA+017 
85  
Montant Charges et frais
No
-
-
Option.
 
MOA+018 
90 u 
Prime nette
No
-
-
Mand.
 
MOA+005 
95  
Frais de fractionnement
No
-
-
Option.
 
MOA+039 
100  
Autres coûts à ajouter à la prime nette
No
-
-
Option.
 
MOA+105 
105  
Taux de prime
No
-
-
Option.
 
PCD+016 
110  
Taux de commission
No
-
-
Option.
 
PCD+005 
115  
Pourcentage des charges
No
-
-
Option.
 
PCD+006 
120  
Pourcentage des frais
No
-
-
Option.
 
PCD+007 
125  
Pourcentage frais et charges
No
-
-
Option.
 
PCD+010 
130  
Pourcentage réduction commerciale
No
-
-
Option.
 
PCD+036 

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