> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : EPRENOTDET - Echange contextuel, données quittance - (Consultation quittance)
- Approved , and is part of release 200601 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info )
( Additional information is present below the details-table )
Version : 1
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  
Quittance
No
-
-
Mand.
 
XEH+03+1 
20  
Date de comptabilisation
No
-
-
Mand.
 
DTM+005:x--x 
30  
Numéro de police
No
-
-
Option.
 
RFF+001+x--x 
40  
Numéro de quittance
No
-
-
Mand.
 
RFF+027+x--x 
50  
Mode d'encaissement de la quittance
Yes
1
Mand.
 
ATT+B003+x--x 
60  
Type de quittance
Yes
2
Mand.
 
ATT+B001+x--x 
70  
Total à payer
No
-
-
Mand.
 
MOA+012 
80  
Prime nette fractionnée
No
-
-
Mand.
 
MOA+013 
90  
Montant commission
No
-
-
Mand.
Zéro éventuel 
MOA+015 
100  
Montant charges
No
-
-
Mand.
FMSA regulation based 20170223 
MOA+016 
110  
Montant frais
No
-
-
Option.
 
MOA+017 
120  
Intermédiaire - Intermédiaire
No
-
-
Mand.
 
PTY+002 
130  
Intermédiaire - Numéro CBFA
No
-
-
Mand.
 
PTY+002+x--x:006 
140  
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
No
-
-
Mand.
 
PTY+002++x--x:002 
150  
Période assurée
No
-
-
Option.
0..n présences 
PER+xxx 
160  
Période assurée - Date de début de période
No
-
-
Mand.
 
PER+xxx - DTM+041 
170  
Période assurée - Date de fin de période
No
-
-
Mand.
 
PER+xxx - DTM+022 
180  
Quittance - indication fin dossier
No
-
-
Mand.
 
XEH+03 

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

Voir dans les BBP le point 5. ( Suivre >Models >Broker Business Processes >Next->... jusqu'à ce point 5)
/ Zie in de BBP het punt 5. ( Volg >Models >Broker Business Processes >Next->... tot aan dat punt 5)
( http://www.telebib2.org/ProcessBB054.htm )