> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 200601 :
Identifier : ICD1xx - - (Données spécifiques des garanties Vie)-
- ( UN/Edifact : added info )
- (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info )
Sender :
Receiver :
Status : 3 - Version : 1
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
Indicator
Identifier
Version
4  
Garantie, type
No
-
-
Mand.
 
5  
Date prestation du capital vie
No
-
-
Option.
 
10  
Date dernière péréquation
No
-
-
Option.
 
15  
Type de solde restant dû
Yes
1
Option.
 
20  
Régime d'imposition de la prestation
Yes
1
Option.
 
25  
Contrat génère des participations bénéficiaires
No
-
-
Option.
 
30  
Contrat assujetti à péréquation
No
-
-
Option.
 
35  
Imposition de la prestation
No
-
-
Option.
 
40  
Capital vie
No
-
-
Option.
 
45  
Capital décès
No
-
-
Option.
 
50  
Participation bénéficiaire acquise vie
No
-
-
Option.
 
55  
Participation acquise décès
No
-
-
Option.
 
60  
Coëfficient multiplicateur ACRA
No
-
-
Option.
 
65  
Taux d'intérêt solde restant dû
No
-
-
Option.
 
69  
Bénéficiaire
No
-
-
Option.
 
70  
Bénéficiaire - Nom officiel
No
-
-
Option.
 
75  
Bénéficiaire - Type de bénéficiaire standard
Yes
1
Option.
 
80  
Bénéficiaire - Type de bénéficiaire acceptant
Yes
1
Option.
 
85  
Bénéficiaire - Bénéficiaire a accepté l'avantage du contrat
No
-
-
Option.
 
89  
Cessionnaire
No
-
-
Option.
 
90  
Cessionnaire - Nom officiel
No
-
-
Option.
 
95  
Cessionnaire - Numéro du dossier
No
-
-
Option.
 
100  
Cessionnaire - Description
No
-
-
Option.
 
110  
Sous-garanties
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.