> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 201901 :
Identifier : M0403 - Demande, liste de quittances / Vraag, lijst kwijtingen - (Demande liste de quittances impayées / Aanvraag van een lijst van onbetaalde kwijtingen)-
- ( UN/Edifact : added info )
- (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info )
( Additional information is present below the details-table )
Sender : Broker
Receiver : Insurer
Status : 3 - Version : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
Indicator
Identifier
Version
10 u 
Message issuing date and time
No
-
-
Mand.
 
20 u 
Message content inventory identifier
No
-
-
Mand.
 
30 u 
Message content inventory version
No
-
-
Mand.
 
40  
Date de début de période
No
-
-
Option.
 
50  
Type de demande des impayés
Yes
1
Option.
 
60  
Commission
No
-
-
Option.
 
70  
Intermédiaire
No
-
-
Option.
 
80 n 
Intermédiaire - Numéro FSMA
No
-
-
Option.
Since 15/7/2017 the FSMA no longer attributes such number 
90 u 
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
No
-
-
Mand.
 
100 u 
Intermédiaire - Code carte d'échange
No
-
-
Option.
 
101 n 
Intermédiaire - Numéro d'entreprise
No
-
-
Option.
Added as FSMA-broker-id abandoned 15/7/2017 
102 n 
Intermédiaire - Numéro unité d'établissement
No
-
-
Option.
Added as FSMA-broker-id abandoned 15/7/2017 
103 n 
Intermédiaire - LEI
No
-
-
Option.
 
130  
Assureur
No
-
-
Option.
 
140 u 
Assureur - Numéro FSMA
No
-
-
Mand.
 
150 u 
Assureur - Code carte d'échange
No
-
-
Option.
 
151 n 
Assureur - Numéro d'entreprise
No
-
-
Option.
 
152 n 
Assureur - Numéro d'unité d'établissement
No
-
-
Option.
 
153 n 
Assureur - LEI
No
-
-
Option.
 
160 u 
Message end
No
-
-
Mand.
 

(*) 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 22. ( Suivre >Models >Broker Business Processes >Next->... jusqu'ŕ ce point 22. )
/ Zie in de BBP het punt 22. ( Volg >Models >Broker Business Processes >Next->... tot aan dat punt 22. )
( https://www.telebib2.org/ProcessBB22.htm )